https://bugs.kde.org/show_bug.cgi?id=468975
Bug ID: 468975
Summary: When machine wakes up with different number of screens
than it fell asleep with, the screen locker can break
("wl_display@1: error 1: invalid arguments for
wl_display@1.get_registry")
Classification: Plasma
Product: kwin
Version: 5.27.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: n...@kde.org
Target Milestone: ---
STEPS TO REPRODUCE
1. Have a laptop and an external screen (in my case, an HDMI screen plugged
into a Thunderbolt dock)
2. Put the machine to sleep with Kickoff > Sleep
3. Unplug the external screen
4. Wake the machine up
OBSERVED RESULT
Roughly 25% of the time, the screen locker breaks with the typical "the lock
screen is broken" message.
EXPECTED RESULT
The lock screen appears.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.2.11-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
System Version: ThinkPad X1 Yoga 4th
ADDITIONAL INFORMATION
There are no crash logs in `coredumpctl`. Journal logs from kwin_wayland reveal
the following:
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Everything else
failed. Need to put Greeter in emergency mode.
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process
exit unregular. Restarting lock.
Apr 25 16:40:14 Liberator kscreenlocker_greet[41400]: The Wayland connection
broke. Did the Wayland compositor die?
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process
exit unregular. Restarting lock.
Apr 25 16:40:14 Liberator kscreenlocker_greet[41385]: The Wayland connection
broke. Did the Wayland compositor die?
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process
exit unregular. Restarting lock.
Apr 25 16:40:14 Liberator kscreenlocker_greet[41367]: The Wayland connection
experienced a fatal error: Invalid argument
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: wl_display@1: error 1:
invalid arguments for wl_display@1.get_registry
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (22)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (23)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (46)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (45)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (56)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (47)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received
delete_id for unknown id (54)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[1664]: error in client
communication (pid 1664)
Apr 25 16:40:14 Liberator kwin_wayland_wrapper[1664]: not a valid new object id
(2), message get_registry(n)
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process
exit unregular. Restarting lock.
Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter Process
encountered an unhandled error: QProcess::Crashed
--
You are receiving this mail because:
You are watching all bug changes.
