Screen locker is broken and unlocking is not possible anymore... again!

We are facing with what seems to be an old problem returning: after some time of inactivity the KDE session goes locked but it became impossible to regain access as the screen shows the following error:

The screen locker is broken and unlocking is not possible enymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
log in and execute the command:
loginctl unlock-session 3
Then log out of the virtual session by pressing Ctrl+D, and switch back to the running session (Ctrl+Alt+F7).

It’s very, very annoying. Disabling screen locker could help… but can’t be considered a solution!

Please check your installation – the repositories being used and, the installed packages.

Looking at a KDE Forum post related to this issue, it seems that the “libwayland-client0” and “libwayland-cursor0” packages may be influencing this issue.
A forcible re-installation of these packages may help to resolve the issue:

# zypper install --force libwayland-client0 libwayland-cursor0

It may well be that, some housekeeping will be enforced to clean up some no longer needed 32-bit libraries – let Zypper remove any indicated conflicting libraries.

Ok, I’ll give it a try.
What if I say that we don’t use, don’t need (and don’t like) Wayland?
Many thanks.

At login select X11 not Wayland

Then, it ain’t the Wayland issue but, it still may be caused by some no longer needed 32-bit libraries –
Please check for any orphaned packages …


Please check for any user or system core dumps:

> coredumpctl

Either use the user “root” to see all the core dumps or, a user in the “systemd-journal” group.

  • In other forums, there’s a mention of the KDE Screenlocker segment faulting.

Once you have the core dump, you’ll have to submit a KDE Bug Report.

1 Like

It’a already set to X11.

Forcing re-installation of libwayland-client0 libwayland-cursor0 didn’t resulted in actions on any 32-bit library.
Anyway an online-update upgraded some X11 e Wayland related packages.
We’ll see in the next days.

Please check for any user or system core dumps:

> coredumpctl

Didn’t found any coredumps, but perhaps because systemd-coredump was not installed (I installed it now).