https://bugs.kde.org/show_bug.cgi?id=461123
Bug ID: 461123
Summary: When waking from standby or leaving the screenlocker a
blackscreen shows "The screen locker is broken and
unlocking is not possible anymore"
Classification: Plasma
Product: kscreenlocker
Version: 5.18.8
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
Often when I wake the computer from standby (roughly every third time) or leave
it with the screen locked for a while, I get a blackscreen displayed for about
1-2 seconds with this:
>The screen locker is broken and unlocking is not possible anymore.
>In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
>log in and execute the command:
>loginctl unlock session 2
>Afterwards switch back to the running session
When I press Ctrl+Alt+F2, login, run `loginctl unlock session 2` (or whatever
the id is which changes) and `logout` and press Ctrl+Alt+F1 I can resume the
session (albeit some apps like Kate are frozen and need to get restarted).
The problem doesn't occur on another machine with nearly the same Debian11/KDE
setup (but a different wallpaper and different CPU). I think the problem may be
caused by my i915 graphics driver (FOSS only; no graphics driver things from
non-free) or my wallpaper. I'm using Wayland and this problem only occurs since
I switched from X11 to Wayland.
Many others have reported this or similar problems too:
https://bbs.archlinux.org/viewtopic.php?id=236664
https://forum.kde.org/viewtopic.php?f=309&t=174343
So this could be a duplicate - I'm interested if there already is a bug to
track or a solution / workaround.
If you close this bug, please don't close it before linking the most related
bug and/or workaround. If there is currently no solution, at least for
Debian11, then some info on what I could try or investigate would be useful
too.
Here I reported a similar bug but it seems like that one is gone now at least
as long as I don't have another display connected with HDMI and is separate to
this problem: https://bugs.kde.org/show_bug.cgi?id=457996
I checked journalctl and these are the first entries when waking from standby
(at the time when the problem occurs):
>org.kde.kiod5[2331981]: qt.qpa.wayland: Creating a fake screen in order for Qt
>not to crash
>org.kde.ActivityManager[2475]: qt.qpa.wayland: Creating a fake screen in order
>for Qt not to crash
>spectacle[63401]: qt.qpa.wayland: Creating a fake screen in order for Qt not
>to crash
>org.kde.krunner[447211]: qt.qpa.wayland: Creating a fake screen in order for
>Qt not to crash
>dbus-daemon[2280]: [session uid=1000 pid=2280] Activating service
>name='org.kde.KSplash' requested by ':1.1239'
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
