[opensuse-factory] login woes after resume
Hi List, just arrived at the office, resumed my laptop which I had suspended at home - and was not able to log in. The lock screen was displayed, the mouse cursor was moving, I could click stuff (like the eye symbol, or the switch user) and start those actions. However clicking the password field did NOT place the focus there, I could NOT put any characters there. THe keyboard itself was fine and the input read: pressing CAPSLOCK produced the warning above the field. Just no password entry. I finally used 'loginctl unlock-sessions' from a VT to unlock it. This however messed up my (dual) screen setup somehow. Looking in the logs I only saw the failed unlock attempts, but nothing that I would relate to the actual issue. Anyone seen it before? I'm at 20180227 at the moment, using standard sddm+plasma5. PS: I had just tried changing the monitor setup using the KDE control center. Pressing 'Apply' to the changed monitor layout completely froze the laptop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
There are several upstream issues related to logind/resume/drm devices, like https://github.com/systemd/systemd/issues/8343 https://github.com/systemd/systemd/issues/8035 you may want to check if anyone is related On Mon, Mar 5, 2018 at 12:41 PM, Peter Suetterlin <pit@astro.su.se> wrote:
Hi List,
just arrived at the office, resumed my laptop which I had suspended at home - and was not able to log in. The lock screen was displayed, the mouse cursor was moving, I could click stuff (like the eye symbol, or the switch user) and start those actions.
However clicking the password field did NOT place the focus there, I could NOT put any characters there. THe keyboard itself was fine and the input read: pressing CAPSLOCK produced the warning above the field.
Just no password entry.
I finally used 'loginctl unlock-sessions' from a VT to unlock it. This however messed up my (dual) screen setup somehow.
Looking in the logs I only saw the failed unlock attempts, but nothing that I would relate to the actual issue.
Anyone seen it before?
I'm at 20180227 at the moment, using standard sddm+plasma5.
PS: I had just tried changing the monitor setup using the KDE control center. Pressing 'Apply' to the changed monitor layout completely froze the laptop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov wrote:
There are several upstream issues related to logind/resume/drm devices, like
https://github.com/systemd/systemd/issues/8343 https://github.com/systemd/systemd/issues/8035
you may want to check if anyone is related
I don't think it is related, but following crosslinks I found mentions of input focus issues, and that seems to be the case. I had a similar issue this morning, and it seems related to having two monitors connected. In todays case, I could nicely enter password in the input field of my laptop screen. But on the second screen, which also shows the lock screen and input fields, I was not able to select the input field and enter anything there. I *could* click the 'login' button though (the password I had entered in the main screen password field). It tried to log in with an empty password and failed. So it looks like there are two separate instances of the locker running.... I now assume that the first time it was the same issue, with the input focus being on the second screen. Unfortunately I did not have a closer look at it the first time, so I'm not sure. But I'd call it reasonable. Guess I'll file a bugreport.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
Peter Suetterlin