Slow shutdown problems

tiykxjoqzbvnlyq · 2021-11-09 04:06:08

I installed arch linux properly and I completely followed the arch wiki and everything is installed properly. But when I shut down my pc I get a message - "/dev/sda3 clean blocks 1254546/13452252" and it takes 1.5 to 2 minutes to shutdown my pc. Its not like I get it everytime but when I get it , it takes 2 minutes for my pc to shut down. Any clue ?

seth · 2021-11-09 07:47:18

Pos t the system journal for the boot w/ the stalled shutdown

sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io # for the previous boot

tiykxjoqzbvnlyq · 2021-11-09 07:50:41

Here - http://ix.io/3Etu

seth · 2021-11-09 08:03:10

Nov 09 11:11:51 rounak systemd[1]: session-2.scope: Stopping timed out. Killing.
Nov 09 11:11:51 rounak systemd[1]: session-2.scope: Killing process 1389 (kwin_x11) with signal SIGKILL.
Nov 09 11:11:51 rounak systemd[1]: session-2.scope: Killing process 1572 (CPMMListener) with signal SIGKILL.
Nov 09 11:11:51 rounak systemd[1]: session-2.scope: Killing process 2011 (QSGRenderThread) with signal SIGKILL.
Nov 09 11:11:51 rounak systemd[1]: session-2.scope: Failed with result 'timeout'.

https://bbs.archlinux.org/viewtopic.php?id=269310
https://bbs.archlinux.org/viewtopic.php?id=269549
https://bbs.archlinux.org/viewtopic.php?id=270759

tiykxjoqzbvnlyq · 2021-11-09 08:08:40

So it is a kde bug right ? I have to logout and then I have to shutdown or I can use shutdown now command to shut it down instantly right ?

seth · 2021-11-09 08:10:51

Logging out and shutting down will work, "shutdown now" most likely not (same problem) - and yes, the bug is somewhere in kde, likely kwin … and I'm still blaming qml.

tiykxjoqzbvnlyq · 2021-11-09 08:16:09

Thank u so much for ur time I though that I installed arch wrong.

PotatoFuhrer · 2021-11-20 01:03:03

I seem to be having the same issue. I came across this thread before and tried the logout then shutdown method to no avail. Yet now it seems to be working after I removed dhcpcd.

Here is my output of:

sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io # for the previous boot

Edit:
Here's my neofetch

Last edited by PotatoFuhrer (2021-11-20 01:05:12)

seth · 2021-11-20 07:56:52

Nov 19 19:57:11 maxbook sddm[332]: Authentication error: "Process crashed"
Nov 19 19:57:11 maxbook sddm[332]: Auth: sddm-helper crashed (exit code 15)
Nov 19 19:57:11 maxbook sddm[332]: Authentication error: "Process crashed"
Nov 19 19:57:11 maxbook sddm[332]: Auth: sddm-helper exited with 15
…
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: State 'stop-sigterm' timed out. Killing.
Nov 19 19:58:41 maxbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: Killing process 332 (sddm) with signal SIGKILL.
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: Killing process 4321 (Xorg) with signal SIGKILL.
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: Killing process 339 (QDBusConnection) with signal SIGKILL.
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: Main process exited, code=killed, status=9/KILL
Nov 19 19:58:41 maxbook systemd[1]: sddm.service: Failed with result 'timeout'.
Nov 19 19:58:41 maxbook systemd[1]: Stopped Simple Desktop Display Manager.
Nov 19 19:58:41 maxbook systemd[1]: Stopping User Login Management...

https://github.com/sddm/sddm/issues/1261
https://bbs.archlinux.org/viewtopic.php?id=256441

The upper segment is also in the journal in #3 but the lower isn't.
You could try to replace sddm w/ eg. startx (but see the 4th link below ;-)

tiykxjoqzbvnlyq · 2021-11-22 14:05:49

So it is a sddm bug right ? So what should I do now ? I dont know how to use .xinitrc properly. so I should copy the xinit file from cp /etc/X11/xinit/xinitrc ~/.xinitrc and then i will remove everything from the .xinitrc file and type exec plasma ?

Last edited by tiykxjoqzbvnlyq (2021-11-22 14:06:13)

seth · 2021-11-22 14:59:04

Certainly not *everything* (then why copy the file to begin with) - only the client programs you don't want to run.
As for what to add: https://wiki.archlinux.org/title/KDE#From_the_console

tiykxjoqzbvnlyq · 2021-11-22 16:04:57

I think I will wait for the sddm devs to fix the bug.

apol · 2021-11-23 23:19:10

This is unlikely an SDDM bug.

Otherwise, would you be able to try enabling systemd boot for Plasma and see if it addresses the problem for you?
https://invent.kde.org/plasma/plasma-wo … stemd-boot

tiykxjoqzbvnlyq · 2021-11-25 08:16:47

seth wrote:

Certainly not *everything* (then why copy the file to begin with) - only the client programs you don't want to run.
As for what to add: https://wiki.archlinux.org/title/KDE#From_the_console

I am facing the same problem and this is my shutdown log. Can u see what went wrong here ?

http://ix.io/3G3o

seth · 2021-11-25 08:25:55

Nov 25 13:29:08 rounak sddm[324]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Nov 25 13:29:08 rounak sddm[324]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Nov 25 13:29:08 rounak systemd[1]: sddm.service: Deactivated successfully.
Nov 25 13:29:08 rounak systemd[1]: Stopped Simple Desktop Display Manager.
Nov 25 13:29:08 rounak audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 25 13:29:08 rounak systemd[1]: sddm.service: Consumed 15.785s CPU time.
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'.
Nov 25 13:30:37 rounak systemd[1]: Stopped Session 2 of User rounak.

same problem as everyone else

tiykxjoqzbvnlyq · 2021-11-25 09:46:25

seth wrote:

Nov 25 13:29:08 rounak sddm[324]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Nov 25 13:29:08 rounak sddm[324]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Nov 25 13:29:08 rounak systemd[1]: sddm.service: Deactivated successfully.
Nov 25 13:29:08 rounak systemd[1]: Stopped Simple Desktop Display Manager.
Nov 25 13:29:08 rounak audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 25 13:29:08 rounak systemd[1]: sddm.service: Consumed 15.785s CPU time.
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'.
Nov 25 13:30:37 rounak systemd[1]: Stopped Session 2 of User rounak.

same problem as everyone else

I already made a bug report regarding it but no answers - https://bugs.kde.org/show_bug.cgi?id=445385

I bet the culprit is kwin_x11 , QDBusConnection and QSGRenderThread

Last edited by tiykxjoqzbvnlyq (2021-11-25 09:49:33)

CatCatCatCatCatCatCat · 2022-05-15 13:22:20

I seem to be having a similar issue as those in this thread, so I'm posting here instead of creating a new one. My issue creates a full minute and a half where SDDM doesn't close. There don't seem to be any in the thread, does anyone have any fixes or workarounds for this? Searching the web it seems like a common issue but none of the fixes seem to work.

May 15 00:02:00 CORE dbus-daemon[497]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
May 15 00:03:29 CORE systemd[1]: sddm.service: State 'stop-sigterm' timed out. Killing.
May 15 00:03:29 CORE systemd[1]: sddm.service: Killing process 528 (sddm) with signal SIGKILL.
May 15 00:03:29 CORE systemd[1]: sddm.service: Killing process 2597 (Xorg) with signal SIGKILL.
May 15 00:03:29 CORE systemd[1]: sddm.service: Main process exited, code=killed, status=9/KILL
May 15 00:03:29 CORE systemd[1]: sddm.service: Failed with result 'timeout'.

V1del · 2022-05-15 15:32:08

please create a new thread this is a different issue.

FWIW as far as fixes go, I'm assuming you are exiting out of a wayland session. You can manually switch to VT1 (ör whatever sddm is on, VT1 will be the default) so sddm actually gets a signal, or try behaviour with sddm-git which has a native wayland backend: https://wiki.archlinux.org/title/SDDM#R … er_Wayland

RounakDutta · 2022-05-16 21:01:11

Hi I am tiykxjoqzbvnlyq replying from my second account because I created my main account with the help of a temp mail service and I lost its password . I am not using kde in Wayland . I have only installed xorg. I already made a bug issue on bugs.kde.org on 2021 and they just gave it a duplicate tag and said that it has already got fixed. I tried plasma with different login managers. Earlier I use to get message like "/dev/sda3 clean blocks 686544/19456452" but nowadays when I shutdown my pc sometimes a blank screen appears with a blinking cursor and it takes literally 2 minutes for it to shut down. Here https://bugs.kde.org/show_bug.cgi?id=445385
In GitHub I already made a issue on it - https://github.com/sddm/sddm/issues/1476
But no response.

Last edited by RounakDutta (2022-05-16 21:15:55)

seth · 2022-05-17 05:43:04

What! The! Fuck!

Status quo:
1. Cat{7,7} is likely experiencing a different problem, at least as can be told from the limited journal segment they posted. That's already pointed out by V1del
2. "But no response." – There're 27 posts on that github issue and 15 on the KDE bug, the last one (falsely) marking it as duplicate.
3. "Create a new issue in Arch Linux forums ....maybe then they might address you." – is flat out trolling for spam by someone who doesn't run arch to begin with, "enjoy your ban", I guess.
4. As pointed out in #4, #9 and #15: this is a very common pattern for many KDE users
5. Coming back to (1): it does however match https://bugs.kde.org/show_bug.cgi?id=445449 which is the (false) duplicate of Rounak's KDE bug and that bug (https://bugs.kde.org/show_bug.cgi?id=445449) cycles back to the SDDM issue (which is not a SDDM issue as indicated by https://bugs.kde.org/show_bug.cgi?id=445449#c14 ) and it might be more akin to https://github.com/sddm/sddm/issues/1261

@CatCatCatCatCatCatCat please post a complete system journal so it can be actually verified whether the SDDM crash is just at the tail of a KDE shutdown

RounakDutta · 2022-05-17 10:12:55

I made another bug request - https://bugs.kde.org/show_bug.cgi?id=453928
Lets hope that they approve this one .
I will post journalctl logs there soon because my journal logs were disabled so I had to set "Storage=persistent" in "/etc/systemd/journald.conf" and I had to reload "systemd-journald.service"

This is my journalctl logs -
When my pc takes time to shut down - http://0x0.st/oaiV.txt
And when my pc shuts down normally - https://0x0.st/oai_.txt

It only happens with plasma and no other desktop environments.

Bruh

 
http://0x0.st/oaiV.txt
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
May 17 15:43:46 archissexy systemd[558]: app-firefox-663133abf48d4c0ab238cf6cc4831123.scope: Consumed 1min 40.732s CPU time.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Stopping timed out. Killing.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Killing process 604 (kwin_x11) with signal SIGKILL.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Killing process 767 (n/a) with signal SIGKILL.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Killing process 2138 (QSGRenderThread) with signal SIGKILL.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Failed with result 'timeout'.
May 17 15:45:14 archissexy systemd[1]: Stopped Session 2 of User rounak.
May 17 15:45:14 archissexy systemd[1]: session-2.scope: Consumed 42.543s CPU time.
May 17 15:45:14 archissexy systemd[1]: Stopping User Login Management...
May 17 15:45:14 archissexy systemd[1]: Stopping User Manager for UID 1000...
May 17 15:45:14 archissexy systemd-logind[427]: Removed session 2.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Last edited by RounakDutta (2022-05-17 10:26:07)

RounakDutta · 2022-05-17 16:18:40

@seth I think found a workaround I guess but will this work ? - https://www.reddit.com/r/ManjaroLinux/c … njaro_kde/
If kwin is not shutting down then I will make a systemd service which stops kwin . In this way I don't have to wait for like 2 minutes for my pc to get shutdown.
Btw I found another thread in archforum. A lot of people are having the same problem

Last edited by RounakDutta (2022-05-17 16:22:35)

RounakDutta · 2022-06-19 17:23:33

Ok so the problem got solved after the new kde update, they did some changes to how kwin handles and terminates tasks. It turns out that kwin was trying to exit when sigterm was given by systemd thats why kwin was hanging. - https://bugs.kde.org/show_bug.cgi?id=453928 . Kudos to the kde team. This bug was making me crazy. They finally fixed it after 2 years!!!! Now the system abruptly shuts down within 5 seconds

Last edited by RounakDutta (2022-06-19 17:31:01)

Arch Linux

#1 2021-11-09 04:06:08

Slow shutdown problems

#2 2021-11-09 07:47:18

Re: Slow shutdown problems

#3 2021-11-09 07:50:41

Re: Slow shutdown problems

#4 2021-11-09 08:03:10

Re: Slow shutdown problems

#5 2021-11-09 08:08:40

Re: Slow shutdown problems

#6 2021-11-09 08:10:51

Re: Slow shutdown problems

#7 2021-11-09 08:16:09

Re: Slow shutdown problems

#8 2021-11-20 01:03:03

Re: Slow shutdown problems

#9 2021-11-20 07:56:52

Re: Slow shutdown problems

#10 2021-11-22 14:05:49

Re: Slow shutdown problems

#11 2021-11-22 14:59:04

Re: Slow shutdown problems

#12 2021-11-22 16:04:57

Re: Slow shutdown problems

#13 2021-11-23 23:19:10

Re: Slow shutdown problems

#14 2021-11-25 08:16:47

Re: Slow shutdown problems

#15 2021-11-25 08:25:55

Re: Slow shutdown problems

#16 2021-11-25 09:46:25

Re: Slow shutdown problems

#17 2022-05-15 13:22:20

Re: Slow shutdown problems

#18 2022-05-15 15:32:08

Re: Slow shutdown problems

#19 2022-05-16 21:01:11

Re: Slow shutdown problems

#20 2022-05-17 05:43:04

Re: Slow shutdown problems

#21 2022-05-17 10:12:55

Re: Slow shutdown problems

#22 2022-05-17 16:18:40

Re: Slow shutdown problems

#23 2022-06-19 17:23:33

Re: Slow shutdown problems

Board footer