Bug 461123 - "The screen locker is broken and unlocking is not possible anymore" with console output saying "Creating a fake screen in order for Qt not to crash"
Summary: "The screen locker is broken and unlocking is not possible anymore" with cons...
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.3
Platform: Fedora RPMs Linux
: VHI grave
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-28 16:30 UTC by myndstream
Modified: 2024-03-30 18:08 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description myndstream 2022-10-28 16:30:15 UTC
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
Comment 1 Bug Janitor Service 2022-10-28 16:33:48 UTC
Thank you for the bug report!

However Plasma 5.18.8 is no longer supported by KDE; supported versions are 5.24, and 5.26 or newer.
Your distribution is responsible for providing support for older versions of KDE software.

Please do one of the following:
- Upgrade to a supported version and see if the issue is still relevant
- Report the issue to your distribution
Comment 2 myndstream 2022-10-28 16:46:26 UTC
(In reply to Bug Janitor Service from comment #1)
> However Plasma 5.18.8 is no longer supported by KDE; supported versions are 5.24, and 5.26 or newer.
The version is 5.20.5 but that version is missing in the dropdown. I just the bug still occurs with newer versions according to a comment, changed the version (it's in Manjaro). And if you close this, please do this:

>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.
Comment 3 myndstream 2022-10-28 16:55:26 UTC
Sorry, can't edit the description: the other computer where this doesn't occur doesn't use Wayland but X11.
Comment 4 myndstream 2022-10-28 17:07:22 UTC
Based on this Q&A, I ran `/usr/lib//usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing` which shows this output:

>qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side, use QT_IM_MODULE=qtvirtualkeyboard at compositor-side.
Locked at 1666976439
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/homeworld-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper-withlogo" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-inksplat-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/wallpapers/Next" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/spacefun-theme/wallpaper" is a directory. Use addDir!
>qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
>Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module >"QtQuick.VirtualKeyboard" is not installed
>qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

There also is a folder /home/username/.cache/kscreenlocker_greet but it's probably irrelevant. The screenlocker has a jpg image and I could post the settings but it probably occurs with all the screenlocking settings.
Comment 5 Nate Graham 2022-10-28 20:13:18 UTC
> file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module >"QtQuick.VirtualKeyboard" is not installed

Does it start working if you install the QtVirtualKeyboard module?
Comment 6 myndstream 2022-10-29 16:11:43 UTC
No, it doesn't. I still get this error. After installing it, the lockscreen has a small keyboard icon and "Virtual Keyboard" in the bottom left and I get this when I rerun the testing command (and I don't think it's possible to set "QT_IM_MODULE=qtvirtualkeyboard at compositor-side"):

>qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side, use QT_IM_MODULE=qtvirtualkeyboard at compositor-side.
Locked at 1667055520
>qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
>qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
>Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/homeworld-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper-withlogo" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-inksplat-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/wallpapers/Next" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/wallpaper" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/lockscreen" is a directory. Use addDir!
>kf.coreaddons: KDirWatch: "/usr/share/desktop-base/spacefun-theme/wallpaper" is a directory. Use addDir!
>qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Also I should have added that sometimes (like one in ten times), it does not shortly display the message, but only displays a black screen with a working mouse cursor (I think when the message displays no mouse cursor is shown). When this occurs this is in the journalctl logs:

>dbus-daemon[2260]: [session uid=1000 pid=2260] Activating service name='org.kde.KSplash' requested by ':1.106' (uid=1000 pid=1504644 comm="/usr/bin/plasmashell ")
>dbus-daemon[2260]: [session uid=1000 pid=2260] Activating service name='org.kde.kdeconnect' requested by ':1.106' (uid=1000 pid=1504644 comm="/usr/bin/plasmashell ")
>dbus-daemon[2260]: [session uid=1000 pid=2260] Activated service 'org.kde.kdeconnect' failed: Failed to execute program org.kde.kdeconnect: Permission denied
>[...(same kdeconnect errors)...]
>dbus-daemon[2260]: [session uid=1000 pid=2260] Activating service name='org.kde.kdeconnect' requested by ':1.106' (uid=1000 pid=1504644 comm="/usr/bin/plasmashell ")
>dbus-daemon[2260]: [session uid=1000 pid=2260] Activated service 'org.kde.kdeconnect' failed: Failed to execute program org.kde.kdeconnect: Permission denied
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-protocol-native" was found
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-client-node" was found
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-client-device" was found
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-adapter" was found
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-metadata" was found
>kwin_wayland[2268]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: Datei oder Verzeichnis nicht gefunden
>kwin_wayland[2268]: No module "libpipewire-module-session-manager" was found
>kwin_wayland[2268]: core 0x5581a2aff430: can't find protocol 'PipeWire:Protocol:Native': Die Operation wird nicht unterstützt
Comment 7 myndstream 2022-10-29 16:19:33 UTC
The first message of the journalctl logs above (before "dbus-daemon[2260]") was missing, it's:
>org.kde.ActivityManager[2407]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Comment 8 mcarans 2022-11-14 21:35:45 UTC Comment hidden (spam)
Comment 9 Nate Graham 2022-11-15 18:01:13 UTC Comment hidden (spam)
Comment 10 Clarence Manuel 2022-11-18 00:27:53 UTC Comment hidden (spam)
Comment 11 kingofgamesyami 2022-11-18 05:05:06 UTC Comment hidden (spam)
Comment 12 Clarence Manuel 2022-11-18 05:38:11 UTC Comment hidden (spam)
Comment 13 Kyle McGrath 2022-11-18 05:47:02 UTC Comment hidden (spam)
Comment 14 hiraniu 2022-11-18 14:07:45 UTC Comment hidden (spam)
Comment 15 mcarans 2022-11-18 18:06:58 UTC Comment hidden (spam)
Comment 16 Nate Graham 2022-11-18 20:45:06 UTC Comment hidden (spam)
Comment 17 Clarence Manuel 2022-11-18 22:12:46 UTC Comment hidden (spam)
Comment 18 Kyle McGrath 2022-11-19 01:33:03 UTC Comment hidden (spam)
Comment 19 ByteEnable 2022-11-19 15:15:50 UTC Comment hidden (spam)
Comment 20 ByteEnable 2022-11-19 16:00:39 UTC Comment hidden (spam)
Comment 21 Nate Graham 2022-11-21 21:10:43 UTC Comment hidden (spam)
Comment 22 Nate Graham 2022-11-21 21:11:35 UTC
myndstream@protonmail.ch, when this happens, does `coredumpctl --reverse` show any crashes for kscreenlocker_greet?
Comment 23 Bug Janitor Service 2022-12-06 05:18:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 24 Bug Janitor Service 2022-12-21 05:20:41 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!