-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cinnamon screensaver fails to wake up #6355
Comments
I would check the system log (/var/log/syslog or journalctl) and the session log (~/.xsession-errors) for any errors that occur. Other than that, I'm not sure where to look. |
Might not be directly related, but I also had a problem with Cinnamon screensaver not waking up, until I tried to press Esc key. Seems obvious, but not when you encounter it for the first time :) |
@onyxnz, is this still an issue in Cinnamon 4.2? |
Every time my computer goes off to the lock screen I can not enter my password. TextBox behaves like it is disabled. Cannot get focus into it and can't type anything. Eventually, after clicking on the "People" icon it will switch to another screen where the password entry TextBox is enabled and I can type my password and get back in. Kind of a PITA |
@dxvictor are you the only user on your computer? Just curious if the original issue has roots in there being multiple users. |
On my system with LinuxMint 18.1 Cinnamon, there are 2 users - the wife and I. When either one of us goes to Switch User, then works on other user for a time, and Switch User to return to the first user, that first user is stuck with the screensaver - the digital clock and picture. Ctrl+L at this point will bring up the lock screen/switch user dialog, but fails to unlock the screen to get back to the desktop.
I have found as a workaround that by dropping to CLI (eg CTRL ALT F2) and killing cinnamon-screensaver for the locked out user that their desktop is suddenly available again on their TTY (eg CTRL ALT F7). So cinnamon screensaver is failing to wake up correctly.
How can I diagnose this further?
The text was updated successfully, but these errors were encountered: