Open dpiotrowski opened 7 years ago
I'll check on this on my LMDE machine today. I did add additional logging at one point, including what travels thru the pipe. I'll put a big warning at the start of logging to warn the user in this mode so they can redact.
I have exactly the same problem here (also LMDE2 on two different PCs). With version 3.2.9 it worked like expected, after the update to 3.2.12 it is not possible to unlock the screen (in a normal way).
Same here on LMDE2 with version 3.2.12. Oddly enough, when I first upgraded to screensaver 3.2.12 (which came with Cinnamon version 3.2.7), no locking occurred at all. This was after just restarting the new Cinnamon.
Then I did a reboot. Now, the first time the screensaver is started, I do get both a locked screen AND the log in prompt. Start the screensaver again, though, the screen does lock, but there is no login prompt, and I'v only been able to resolve this by restarting via Ctrl+Alt+Backspace.
Same issues here after 12/22/2016 updates to the following packages: libcscreensaver0 from 3.2.9+betsy to 3.2.12+betsy cinnamon from 3.2.6+betsy to 3.2.7+betsy cinnamon-common from 3.2.6+betsy to 3.2.7+betsy cinnamon-screensaver from 3.2.9+betsy to 3.2.12+betsy
Should be fixed by https://github.com/linuxmint/cinnamon-screensaver/commit/0cf592af37f65229157712d40123b5931ff9a164 - just waiting on a new release, coming asap.
If you don't want to wait, you can edit the installed file (sudo gedit /usr/share/cinnamon-screensaver/manager.py
) and move the line in that commit yourself (just restart the screensaver or log out/in.)
@mtwebster I've edited the file manually, restarted cinnamon-screensaver and tested. It seems to work OK :) Thank you!
Thanks Michael. Works great. :D
On Wed, Dec 28, 2016 at 2:38 AM Dawid Piotrowski notifications@github.com wrote:
@mtwebster https://github.com/mtwebster I've edited the file manually, restarted cinnamon-screensaver and tested. It seems to work OK :) Thank you!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-screensaver/issues/190#issuecomment-269451999, or mute the thread https://github.com/notifications/unsubscribe-auth/APXR5SpCzyns4889iEs1pZTpzfH5x2vXks5rMi4bgaJpZM4LU5xx .
I am facing this in linux mint 18.1
I checked the code, the fix is included but the issue still persist
@mtwebster any ideas?
I checked the code, the fix is included but the issue still persist I too (in LMDE)
Just a guess but it's possible that one of the python dependencies is not installed on your system so the code is not compiling. You can look in the code to see what they are and verify that they are installed.
Also, be sure to logout or restart your computer so that it has a chance to compile the new code when you login again.
On Jan 4, 2017 2:00 PM, "rena" notifications@github.com wrote:
I checked the code, the fix is included but the issue still persist I too (in LMDE)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-screensaver/issues/190#issuecomment-270485091, or mute the thread https://github.com/notifications/unsubscribe-auth/APXR5fW97Jd8_Ja2mcdCY4NDgwb1va_3ks5rPAhxgaJpZM4LU5xx .
Reiterating what was just said, make sure you log out/in or kill and restart the screensaver.
I'm seeing this behavior today after a full power down restart. Mint 18.3. Didn't start until the kernel update that came out yesterday, if that helps anything.
Still reproducible here on AOSC OS, version 3.6.1.
Experiencing this on an up to date Arch machine today with (kernel 5.19.3)
$ cinnamon-screensaver-command -l
Traceback (most recent call last):
File "/usr/bin/cinnamon-screensaver-command", line 98, in _on_proxy_ready
self.perform_action()
File "/usr/bin/cinnamon-screensaver-command", line 115, in perform_action
self.proxy.call_lock_sync(self.message)
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method Lock is not implemented on interface org.cinnamon.ScreenSaver (19)
Various other online solutions regarding subprocess.run.pth
don't seem to resolve it. Screen locks but has no password prompt upon interaction.
Hi After updating from 3.2.9 to 3.2.12 on LMDE2, cinnamon-screensaver I'm having issues with unlocking the screen. When I try to unlock the screen, the password prompt doesn't appear for some time. In order to unlock the screen I need to do a considerable amount of random key pressing, though the amount of pressing does not seem to be consistent across attempts.
When I tried killing cinnamon-screensaver and running it with
--debug
the output I got was (first attempt with a faux password, the second with the correct one):Additional quirk in case you overlooked it: --debug now prints the actual password you type in at the login prompt. Is it supposed to do that? Last time I checked (version 3.2.8) it didn't print any such thing.
Expected behaviour: when the screen is locked pressing a button or moving the mouse should bring the password prompt immediately.