Page MenuHomeSolus

Can't get focus on password field on lock screen
Closed, ResolvedPublic

Description

Sometimes it's impossible to get focus and type the user password after locking the screen.
I am not currently able to reproduce it since it seems quite random but it happens specially when the screen locks automatically after turning off.
PC is not freezed since "Unlock" button works (clearly responding with an incorrect password message): the only solution is keep pushing the power button :(
I'll keep testing to see if it depends on a particular power/setting condition

Event Timeline

giangi74 updated the task description. (Show Details)Oct 19 2016, 10:37 PM

I found the reason.
If you are running a full screen application (I was using xfreerdp to manage a remote server) and the PC goes to blank screen, if you have set password lock you can't type in your password anymore.
The only way is to power off!

JoshStrobl triaged this task as Normal priority.Oct 28 2016, 9:23 PM
JoshStrobl edited projects, added Software; removed Triage Team.
JoshStrobl moved this task from Backlog to System and Configuration Fixes on the Software board.

Confirmed behavior also running VirtualBox in full screen mode.

I can also confirm this behavior using VMware View client in full screen.
If I try to minimize the VMware full-screen after awhile (screen saver time), then the screen saver locks the screen but I can't type the password.
I could switch to a console with Alt-Ctrl-F1 and kill the screensaver to get back control.
For now I disabled the screen lock, but hope it can be fixed soon.

I have the very same problem. Just today I was unable to unlock the screen, the cursor in the password field didn't show up but it was possible to push the unlock button getting the message that the password was incorrect. Here, they report the same behavior: T281. I entered into a console with Ctrl+Alt+F2 and rebooted with sudo reboot, thereby avoiding a hard reset. I closed the lid of my laptop yesterday evening, I was able to open it and unlock the screen this morning after pushing the power button, but failed to unlock after the screen locked itself again.

Maybe this output from journalctl -u lightdm helps:
Jan 31 16:21:04 le_acer lightdm[597]: Could not enumerate user data directory /var/lib/lightdm-data: Error opening directory '/var/lib/lightdm-data': No such file or directory
Jan 31 16:21:06 le_acer lightdm[597]: Could not create user data directory /var/lib/lightdm-data/lightdm: Error creating directory /var/lib/lightdm-data/lightdm: No such file o
Jan 31 16:21:06 le_acer lightdm[671]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jan 31 16:21:15 le_acer lightdm[597]: Could not create user data directory /var/lib/lightdm-data/nadler: Error creating directory /var/lib/lightdm-data/nadler: No such file or
Jan 31 16:21:15 le_acer lightdm[713]: pam_unix(lightdm:session): session opened for user nadler by (uid=0)
Feb 01 08:17:31 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/10, but it's already registered
Feb 01 08:17:32 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/11, but it's already registered
Feb 01 08:17:42 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/7, but it's already registered
Feb 01 08:17:42 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/8, but it's already registered
Feb 01 08:17:52 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Feb 01 08:17:52 le_acer gnome-keyring-daemon[724]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered

Justin added a subscriber: Justin.Feb 3 2017, 12:19 AM
timoll added a subscriber: timoll.Feb 21 2017, 12:17 PM

Experienced the same issue.

There is a workaround to unlock the screen.

CTRL + ALT + F1 bring tty1, login my account, then

sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id

And then go back to tty7 with CTRL + ALT + F7.

http://askubuntu.com/questions/557833/how-to-unlock-locked-session/611611#611611

I see issues with VirtualBox on fullscreen, in my case it was not in fullscreen. (It was minimal though, only titlebar, menubar and statusbar)

siru added a subscriber: siru.Mar 17 2017, 5:26 PM

Confirming that the workaround @timoll mentioned works over here.

I also had VirtualBox running - not full screen but the cursor was being captured within a virtual desktop