Bug 476334 - kscreenlocker_greet broken after wakeup
Summary: kscreenlocker_greet broken after wakeup
Status: RESOLVED DUPLICATE of bug 474811
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: git-stable-Plasma/5.27
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-30 18:43 UTC by sherifmuh65
Modified: 2023-11-12 23:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sherifmuh65 2023-10-30 18:43:44 UTC
SUMMARY
Hello everyone,
I have a laptop (ryzen Zen2, integrated graphics) with ARCH Linux KDE plasma (Wayland session). When I wake up it from suspend, it shows the black screen  "The screen locker is broken... loginctl unlock-session ..." 
It happens only if external monitor (HDMI) was connected before sleep. 


STEPS TO REPRODUCE
1. Connect external monitor to laptop
2. Suspend laptop
3. Disconnect external monitor from laptop 
4. Wake up

OBSERVED RESULT
Black screen with message "The screen locker is broken and unlocking is not possible... loginctl unlock-session ..." 

EXPECTED RESULT
Plasma lockscreen 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux
KDE Plasma Version: 5.27
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
journalctl -b

Oct 30 20:16:53 pc kernel: traps: kscreenlocker_g[2642] general protection fault ip:7f75cd44c1a8 sp:7ffe0a6bad18 error:0 in libQt5Qml.so.5.15.11[7f75cd2a7000+281000]
Oct 30 20:16:53 pc kwin_wayland_wrapper[1022]: not a valid new object id (2), message get_registry(n)
Oct 30 20:16:53 pc kwin_wayland_wrapper[1022]: error in client communication (pid 1022)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (60)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (31)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (51)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (41)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (47)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (92)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (42)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (23)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: error: received delete_id for unknown id (22)
Oct 30 20:16:53 pc kwin_wayland_wrapper[2805]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry
Oct 30 20:16:53 pc kscreenlocker_greet[2805]: The Wayland connection experienced a fatal error: Invalid argument
Oct 30 23:16:53 pc kscreenlocker_greet[2810]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 30 23:16:53 pc kscreenlocker_greet[2810]: The Wayland connection broke. Did the Wayland compositor die?
Oct 30 23:16:53 pc kscreenlocker_greet[2814]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 30 23:16:53 pc kscreenlocker_greet[2814]: The Wayland connection broke. Did the Wayland compositor die?
Comment 1 Andreas Sturmlechner 2023-11-12 23:40:29 UTC

*** This bug has been marked as a duplicate of bug 474811 ***