Bug 501433 - Slow shutdown/reboot in arch linux with kwin_x11.service stop sig-term and USER UID 1000.service error.
Summary: Slow shutdown/reboot in arch linux with kwin_x11.service stop sig-term and US...
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: platform-x11-standalone (show other bugs)
Version: 6.3.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: X11-only
Depends on:
Blocks:
 
Reported: 2025-03-13 03:37 UTC by Garima60000
Modified: 2025-03-25 03:00 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 Garima60000 2025-03-13 03:37:15 UTC
SUMMARY
If you shutdown your system from the gui or shutdown now, the system will give sometimes give an error with UID 1000 service with a timeout of 2m or 1m30s and before that it will not shutdown, likely.
I have logs at the end.

STEPS TO REPRODUCE
1.  Shutdown/reboot your System from the gui of the application menu.
2.  There is a chance that a USER UID 1000 service error will break out.

OBSERVED RESULT
If the issue happens, then the system will shutdown slowly with a timer of 1m30s or 2m.

EXPECTED RESULT
Quick shutdown in under 2 seconds which I achieve normally.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch Linux
KDE Plasma Version:  6.3.3
KDE Frameworks Version:  6.11.0
Qt Version:  6.8.2

ADDITIONAL INFORMATION
This issue has been happening even when I used to use debian with kde plasma and I recently switched to arch linux, but it also has this error. When I shutdown normally, there is a chance that the system will show the UID 1000.service stop job error and will slow down the boot to a ridiculously slow time.

One user in github pointed out that it's a bug with kde plasma so I came here in the kwin section. The error he pointed out was plasma-kwin_x11.service: State 'stop-sigterm' timed out. Killing.

One user in arch linux forums pointed out that-
Mar 09 16:46:53 G31M-ES2L systemd[543]: Stopping KDE Window Manager...
…
Mar 09 16:46:53 G31M-ES2L sddm[488]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Mar 09 16:46:53 G31M-ES2L sddm[488]: Auth: sddm-helper (--socket /tmp/sddm-auth-672d500d-4a2f-4b82-b0a6-f9811d0c7550 --id 1 --start /usr/bin/startplasma-x11 --user ak) crashed (exit code 1)
Mar 09 16:46:53 G31M-ES2L sddm[488]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Mar 09 16:46:53 G31M-ES2L sddm[488]: Auth: sddm-helper exited with 1
…
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]: XIO:  fatal IO error 4 (Interrupted system call) on X server ":0"
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]:       after 51 requests (51 known processed) with 0 events remaining.
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]: The X11 connection broke: I/O error (code 1)
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: State 'stop-sigterm' timed out. Killing.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Killing process 768 (kwin_x11) with signal SIGKILL.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Killing process 812 (n/a) with signal SIGKILL.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Main process exited, code=killed, status=9/KILL
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Failed with result 'timeout'.

kwin_x11 (the window manager) doesn't terminate, even though the X11 server is gone.
dr. konqi doesn't kick in (this was also an issue because it kept the session open/renewed it/whatever)

I tried posting about this on arch linux-
https://bbs.archlinux.org/viewtopic.php?pid=2231316#p2231316

Also created an issue about this in github sddm-
https://github.com/sddm/sddm/issues/2058

Here are the logs, they are a bit old but they are what I have right now.
http://0x0.st/8u5x.txt

Thanks,
LL
Comment 1 Garima60000 2025-03-13 03:41:41 UTC
Here is the log of my previous boot, I think the issue also happened here.
Comment 2 Garima60000 2025-03-13 03:41:54 UTC
(In reply to Garima60000 from comment #1)
> Here is the log of my previous boot, I think the issue also happened here.

http://0x0.st/8Snv.txt