If locking was requested while any context menu is shown on the screen,
screensaver is blocked. That's a known issue, and is kind of expected
behavior. However, after context menu closed, xfce4-screensaver starts up. And
after that, there is no way to enter a password, as input field doesn't allow
To reproduce the issue, run in terminal:
sleep 5; xfce4-screensaver-command -l
After command is started, open any context menu. Wait for about 5 seconds to
make sure xfce4-screensaver-command is called. Then dismiss context menu. Then
after screensaver starts, try to unlock.
On debian's xfce4-screensaver-0.1.3-2, I'm having a similar problem.. often times, the password field is not & can not be focused. As a workaround, I press ALT+S to trigger the switch user function which allows me to unlock the session.
oh what also seems to work is to instantly start typing something instead of waiting for the login prompt to show up.. Does that work for you Rinat?
(In reply to Marcel Partap from comment #2)
> oh what also seems to work is to instantly start typing something instead of
> waiting for the login prompt to show up.. Does that work for you Rinat?
I tried to reproduce it again a number of times, and on one occasion having context menu opened during lock up didn't have any effect. But when issue triggers, fast typing doesn't help. Trick with user changing is a workaround, however.
Sean Davis referenced this bugreport in commit 20df0e3b2d5aba5781be89a2c905c8c2094123cd
Fix password entry after stealing focus (bug #15042)
This issue is resolved with the above commit. The screensaver's behavior of unsetting X11 input focus left it in limbo and not directly recoverable. With the above commit, input focus is given to the screensaver after it has been stripped.
I've just tried code before and after commit 20df0e3b2d5aba5781be89a2c905c8c2094123cd, and it's indeed fixing the issue reported. Also tried current state of master branch. It works as desired too.