Cannot unlock XScreenSaver after switching keyboard language

[teknico]

Qubes OS version:

R4.0 (originally installed at 4.0-rc5)

Affected component(s):

XScreensaver

---

Steps to reproduce the behavior:

• lock the screen (either manually or by waiting long enough)
• type the user password
• click the OK button, or press the Enter key

Expected behavior:

Going back to desktop

Actual behavior:

Unlocking is refused with message: "Authentication failed!"

General notes:

The password does works at the initial login with the same username.

Desktop access can be regained with the following workaround:

• press Ctrl-Alt-F2
• login with the same username and password
• run the command: sudo killall xscreensaver
• press Ctrl-Alt-F1

---

Related issues:

Cannot find anything relevant in log files in /var/log/.

In the Qube Manager, the menu entry Qube -> Logs is always empty, irrespective of which qube is selected.

[esote]

@teknico Do you still experience this issue?

[teknico]

Not able to check anymore, sorry.

[majorminors]

I believe this has occurred to me twice. Same Qubes version. Doesn't happen every time the screen locks though. Haven't tried the workaround but I will if it happens again. Just held the power button until the pc turned off and on reboot, the pc returned to normal operation.

Let me know if there's anything you want me to try if it happens again.

[donob4n]

Just an idea... Has your password some rare symbols that could change if the keyboard language is changed?

[majorminors]

Yep! And I regularly toggle between US, US deadkey, and UK keyboards. I'll check to see if the keyboard has changed next time it happens.

Also, in the interim, this happened a third time, and I confirm @teknico's workaround works.

[andrewdavidwong]

Keyboard layout switching was also mentioned in #1917.

[github-actions]

This issue is being closed because:

• This issue is on the "Release 4.0 updates" milestone.
• Qubes OS 4.0 reached EOL (end-of-life) over one year ago.
• There has not been any activity on this issue in over one year.

If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment.
(For example, if a bug still affects Qubes OS 4.1, then the comment "Affects 4.1" will suffice.)