-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow shutdown problems in kde plasma with sddm #1476
Comments
There's measures in #1460 that should mitigate this issue. Also in Plasma Workspace we added f377696bff39e35ae0f7ae6104d8732b3856744e exactly for that. Could you try enabling systemd boot for Plasma and see if it addresses the problem for you? |
Oh thats nice
Can u tell me how to enable systemd boot? I am a noob when it comes to linux. 😅 |
I wouldn't want to be responsible for your system, let me comment in the bug reports you mentioned. |
Today I faced the slow shutdown problem again and this is my shutdown log (journalctl) can u see what went wrong ? |
This lines seems sus ngl - Nov 25 13:30:37 rounak systemd[1]: session-2.scope: Stopping timed out. Killing. Nov 25 13:30:37 rounak systemd[1]: session-2.scope: Killing process 557 (kwin_x11) with signal SIGKILL. Nov 25 13:30:37 rounak systemd[1]: session-2.scope: Killing process 1055 (QSGRenderThread) with signal SIGKILL. Nov 25 13:30:37 rounak systemd[1]: session-2.scope: Failed with result 'timeout'.` |
People having the same issue here I think it is a sddm issue or a kwin issue - https://bbs.archlinux.org/viewtopic.php?id=259577 |
https://bugs.kde.org/show_bug.cgi?id=445449 < same bug in KDE |
FTR, I can reproduce this issue with x11 greeter but not wayland greeter. https://bugs.kde.org/show_bug.cgi?id=445449#c23 With X11 greeter, Xorg terminates and SDDM decides to restart it, at which point the shutdown hangs. |
Just started having the same issue today, because I switched to Wayland. Screen turns black and backlight doesn't when initiating shutdown/reboot, only after a couple of minutes it completely does. Doesn't happen on X11 session, shutdown/reboot is quick. |
Having the same issue on Gentoo https://bugs.gentoo.org/833059 |
Started having exact same issue yesterday on Arch with KDE Plasma on Wayland |
This appears to have been remediated for Fedora Rawhide. |
Having the same issue on Debian Sid. |
This fixed the issue for me, thanks. |
"Arch Linux" should probably be redacted from the title, because this affects Fedora. |
doesn't work on Wayland session. Problem is on Kwin + Wayland. |
I can also confirm, using kwin and wayland, I tried with and without the configuration change and either way it times out, but logging out first makes reboot within like a second. |
Having the same problem with my Wayland sessions with Sway. SDDM fails to properly stop when I trigger a shutdown while a Wayland session is running, but if I log out and return to SDDM's login screen, then shutdown/reboot works without error. I enabled systemd debugging as described here and saw this in the log when I triggered a reboot (
Just trying to say this issue is not specific to KDE. |
Also affected by this. Have noticed that switching ttys while sddm is blocking the shutdown process is a workaround. Specifically, I hit Ctrl+Alt+F3 and then Ctrl+Alt+F2, which causes the sddm job to stop successfully. |
This comment was marked as resolved.
This comment was marked as resolved.
I have noticed another workaround is to log out of your kde session before shutting down. There is never a hang when logging out first. |
I tried to install SDDM from the |
Ok so it is not due to sddm I tried plasma with different login manager like light dm and everytime plasma hangs when shutting down. So I think it is a problem with kwin. I made a new bug report in bugs.kde.org - https://bugs.kde.org/show_bug.cgi?id=453928 |
Well, a kwin developer posted a pull request to fix the issue here #1515 so i think that they already know what is going on. Hopefully they can find some time to update it and fix the issue. |
That pull request is open since february. I mean no response. I already asked people in arch forums and they think that there is something wrong with kwin - Bruh. Look at my logs I am using lightdm but still I am facing the same issue - http://0x0.st/oaiV.txt I think I will use xinitrc (startx script) . |
https://bugs.kde.org/show_bug.cgi?id=427373 - Another one EDIT - Here is the detailed screenshot of the bug I am experiencing - https://imgur.com/a/BWnCXhh |
OK, to clarify this once and for all: In SDDM 0.18.1 (and presumably 0.19.0) there is a shutdown delay (of 30s or whatever your systemd is set to wait to send a SIGKILL). I can replicate this on Gentoo repeatedly with package version 0.18.1 on my system. If I build the code from 'develop' there is no shutdown delay. I haven't bisected to see where the fix is, but it will be resolved for 0.20.0. |
Nice, I was using version |
I can also confirm that sddm-git (AUR package) fixes the issue. Hopefully the 0.20 will be pushed out for everyone else soon. |
Fixed for me. Not exactly sure which component/version update fixed it but it doesn't happen anymore. |
How ? I am getting this message when I am shutting down my pc -https://imgur.com/a/v2k3PnD , https://imgur.com/V0l2RAb It is still taking 2 minutes for it to shut down. |
Try installing the latest git version of sddm, it worked for me. Which Linux distro? |
Arch btw |
still having the same problem. I am using NVIDIA drivers and Installed the sddm-git version through AUR. Thanks for the help btw. I am closing this issue for now because this is not what I really meant. I know it is a kwin bug. I have already moved to i3 window managers and after using linux for like 4 years I understood the more bloat you add to a de, more bugs you will face. I tried gnome, xfce and faced no bugs but kde is just horrible. I don't know maybe I should blame nvidia and not linux. |
I have a vanilla Arch install with KDE plasma and had the same issue with both Xorg and Wayland. However, reading some sddm related issues on kdde arch wiki gave a hint that it is better to use a rootless sddm install. I used paru to install sddm-git and substitute the previous sddm install. Then I had no longer issues like mentioned here #1476 (comment) |
Are u using nvidia? I am using nvidia |
AMD for me. |
AMD and Intel are great for Linux but I use nvidia. Fuck you nvidia |
I had this issue a while back, I lowered the timeouts and it worked for a while, but after recent updates the issue came back. It seems that after recent updates, systemd configs overrides should be set under "user" rather than "system", for example: $ cat /etc/systemd/user.conf.d/99-stop-fast.conf
To find out what's hanging during your shutdown, run Source of the solution: https://bugs.kde.org/show_bug.cgi?id=456713 |
I can confirm for ArchLinux/ArcoLinux that sddm-git is working for us and does NOT have a slow shutdown with Hyprland Alternative solutions:
|
+1 One more solution: |
I too uses Hyprland and installing sddm-git from the AUR fixes it. Although it's unclear which commits fixed it. Probably this? |
|
Has this been fixed in sddm 0.20? |
Yes. |
SDDM >= 0.20.0 has fixed sddm/sddm#1476 and it's no longer necessary to install the lastest development version.
SDDM >= 0.20.0 has fixed sddm/sddm#1476 and it's no longer necessary to install the lastest development version.
Whenever I try to shutdown my pc I get a message like -
"Starting version 249.5-3-arch
/dev/sda3: clean, 458192/30228480 files, 32189479/120907009 blocks "
and it basically takes my pc 2 minutes to shutdown.
People already made a lot of bug request regarding this -
https://bugs.kde.org/show_bug.cgi?id=445449
https://bbs.archlinux.org/viewtopic.php?pid=2002140#p2002140
https://bugs.kde.org/show_bug.cgi?id=445385
Any clue ?
The text was updated successfully, but these errors were encountered: