https://bugs.kde.org/show_bug.cgi?id=487851
Bug ID: 487851
Summary: KWin Wayland crashes on wake with s2idle
Classification: Plasma
Product: kwin
Version: git-stable-Plasma/6.1
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: s...@datagirl.xyz
Target Milestone: ---
Created attachment 170025
--> https://bugs.kde.org/attachment.cgi?id=170025&action=edit
journalctl output showing kwin_watchdog being triggered
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
SUMMARY
When a system using s2idle for suspend wakes up, the systemd watchdog for
kwin_wayland can trigger, causing KWin to quit. This causes the user to lose
their running session.
STEPS TO REPRODUCE
1. Ensure `/sys/power/mem_sleep` is set to "s2idle".
2. Put the system into sleep mode, and wait some time (5-10 minutes appears to
work).
3. Wake up the system.
OBSERVED RESULT
The lock screen appears for a moment before the screen blanks and the user is
returned to SDDM.
>From the logs, KWin is sent SIGHUP and seems to try to recover, but ultimately
terminates.
EXPECTED RESULT
The lock screen appears normally and the user can log back into their running
session.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux
(available in About System)
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
ADDITIONAL INFORMATION
This appears to be an issue affecting systemd more than KWin, and is already
known (see https://access.redhat.com/solutions/5118401). Unfortunately, my
laptop doesn't support S3/deep sleep (possibly due to ACPI?):
# cat /sys/power/mem_sleep
[s2idle]
# echo "deep" > /sys/power/mem_sleep
-bash: echo: write error: Invalid argument
I've been able to work around this by changing WatchdogSec in my
plasma-kwin_wayland.service override:
[Service]
WatchdogSec=3m
It seems like the s2idle interrupts never cause the clock to count up that
high, but there are cases where it could (ex.,
https://github.com/systemd/systemd/issues/9538).
--
You are receiving this mail because:
You are watching all bug changes.
