F24 KDE plasma - shutdown hangs for minutes

[tnsupport]

When shutting down KDE Plasma, after clicking shutdown button and seeing processes shut down, it hangs on Fedora symbol for several minutes

any fix ?

also - can't drag shutdown menu to panel so have to got thru menus each time - any way to add shutdown button to panel ?

[jbuckley2004]

I timed it last night. It took almost exactly 6 minutes to shut down. Somethings not right.
In this thread - http://forums.fedoraforum.org/showth...16#post1764716 - it was suggested that the DefaultTimeoutStopSec parameter in the file /etc/systemd/system.conf be changed from 90 to 30 seconds (followed by a re-boot before it takes effect). But that doesn't seem to have the desired effect.

Instead of going to the shutdown menu, I suggest using alt+F2 to bring up the Plasma Search thingy (you'll see it at the top of the screen). Then just type in "shutdown" or "reboot" (no quotes). It's a great little tool for bringing up apps too, or anything that you might use the two-or-three-clicks-necessary application launcher for.

[rbrick49]

there was a stack of updates this morning but it appears no fix for this shutdown prpblem,its a pain in the butt

[Archangel]

When shutting down KDE Plasma, after clicking shutdown button and seeing processes shut down, it hangs on Fedora symbol for several minutes

any fix ?

also - can't drag shutdown menu to panel so have to got thru menus each time - any way to add shutdown button to panel ?

If the updates didn't fix the shutdown delay:

<--o=o--> A stop job us running for Session 1 of user $USER (1m 29s/1m 30s)

you can do the following:

Open Settings > System Settings.
Navigate to Systemd and look for systemd-sysctl.service

Right-click on the unit and select Edit unit file.
Scroll to the bottom of the configuration and change TimeoutSec= to how many seconds you prefer.

Test by rebooting.

[rbrick49]

If the updates didn't fix the shutdown delay:

<--o=o--> A stop job us running for Session 1 of user $USER (1m 29s/1m 30s)

you can do the following:

Open Settings > System Settings.
Navigate to Systemd and look for systemd-sysctl.service

Right-click on the unit and select Edit unit file.
Scroll to the bottom of the configuration and change TimeoutSec= to how many seconds you prefer.

Test by rebooting.

sorry that didnt work

[Kirys]

My shutdown hung too, is there any way to see what it is waiting for?

[stratacast1]

Hey, I thought I would chime in on this, as I have seen this issue explained by the KDE team. I don't know what version Fedora is running but I found some probably disheartening information. The KDE team has released the KDE Neon User Edition that is based on Kubuntu 16.04 and one of their known issues is the problem you're having. Their version is 5.6.90 and as far as I'm aware there's no fix at this time. It appears there is a conflict with systemd

https://bugs.kde.org/show_bug.cgi?id=363851

[Kirys]

It look much more like another systemd "screwup standard behavior" than a conflict.

[milan]

Hi All.
This is my last shutdown (cca 2min). Maybe somebody will see something interesting there.
F24 KDE Plasma has now more problems (on my machine) for example:
- missing icons in taskbar and appmenu
- cannot start clementine
- audacity starts without controls
etc.

Now that shutdovn

# journalctl --boot=-1

I hope You will see it.

http://pastebin.com/Ef0sf3ht

Milan

[marko]

I would think it would be informative to see if KDE is really involved. Try using "logout" to leave KDE instead of "shutdown" so you get to the sddm / kdm / gdm login page. If that's quick then KDE is not involved, then do the shutdown from the login page to confirm that that is slow. If slow, then it's likely a systemd problem. Or more accurately, systemd tries to shutdown the services but some services don't cleanly or quickly shutdown. I currently seem to have problems with MondoDB 3.2.7 ("stop job is running....").

[milan]

I have autologin turned on.
Logging out and back in takes about 40 sec.
So I think KDE is not involved.

[rbrick49]

I would think it would be informative to see if KDE is really involved. Try using "logout" to leave KDE instead of "shutdown" so you get to the sddm / kdm / gdm login page. If that's quick then KDE is not involved, then do the shutdown from the login page to confirm that that is slow. If slow, then it's likely a systemd problem. Or more accurately, systemd tries to shutdown the services but some services don't cleanly or quickly shutdown. I currently seem to have problems with MondoDB 3.2.7 ("stop job is running....").

ok marko that worked for me heres my log
https://paste.fedoraproject.org/384391/14668186
this log was done 1 week ago

[milan]

Nice.
Restart with working KDE - 1 min.
Shutdown - 1min 40 sec

[rbrick49]

Nice.
Restart with working KDE - 1 min.
Shutdown - 1min 40 sec

since I tried the fix marko posted it shuts down instant

[rbrick49]

I have gone to another distro that works