Long shut down

[Robgoss]

Hello everyone this is my first time posting here so I hope this is the correct forum for this

I just installed Kubuntu 16.04 but I notice every time I shut my machine down I get this message

Message I receive:

a stop job is running for Session c13 of user XX (Xs / 1min 30s)

It takes some time to shut down is there anyway to correct this problem

Thanks so much

[Snowhog]

The short answer is 'no'. I have the same issue and have reported it, but not gotten what I concider a good response, specifically with regards to how to prevent it. That said, if you log out of the Desktop session first, and then when you are back to the Login screen, click on the Poweroff icon, you will not experience this issue. It's what I do now.

[Robgoss]

This is my first time using Kubuntu but I do have many other distributions on other machines and never had this issue I've seen some others complaining about this same issue but have not seen a fix for it.

Thanks so much

[Rog131]

Reduce the waiting ... give the permission to kill



Arch - Problems with latest systemd 226-3: https://bbs.archlinux.org/viewtopic.php?id=203112
-> Reduce the wait time: https://bbs.archlinux.org/viewtopic....69285#p1569285

Give systemd the permission to kill ( default with the later versions)
-> Debian bug reports - systemd kill background processes after user logs out: https://bugs.debian.org/cgi-bin/bugr...cgi?bug=825394

From the changelog of systemd version 230:
systemd-logind will now by default terminate user processes that are
part of the user session scope unit (session-XX.scope) when the user
logs out.
...
/etc/systemd/logind.conf:
KillUserProcesses=yes

[Snowhog]

KillUserProcesses=yes didn't resolve the issue for me; I tried it. In fact, that 'solution' was suggested when I reported the issue. For some it 'apparently' works, but not for all.

But, as I stated, doing a Desktop session logout first and then shutting down from the login greeter screen does work (for me). I reported that also.

[Robgoss]

KillUserProcesses=yes didn't resolve the issue for me; I tried it. In fact, that 'solution' was suggested when I reported the issue. For some it 'apparently' works, but not for all.

But, as I stated, doing a Desktop session logout first and then shutting down from the login greeter screen does work (for me). I reported that also.

Yes your suggestion work but only as a temporary fix there should be a fix for this issue

Thanks

[Snowhog]

Really, performing a user session logout and then shutting down, is a 'better' practice. I don't mind the extra step.

[Robgoss]

Really, performing a user session logout and then shutting down, is a 'better' practice. I don't mind the extra step.

Yes I know what you're saying and thanks

[jglen490]

Really, performing a user session logout and then shutting down, is a 'better' practice. I don't mind the extra step.

Actually, that's true for a NOT well-mannered OS.

[Rog131]

...and with

Bug 363851 - "A stop job is running for Session 1 of user neon" during shutdown: https://bugs.kde.org/show_bug.cgi?id=363851


28 & 29 https://bugs.kde.org/show_bug.cgi?id=363851#c28

Harald Sitter 2016-08-09 08:25:33 UTC
I think this should be solved in dev editions within the hour and for user edition some time this week.

http://packaging.neon.kde.org/cgit/n...a2ef35a31430b6

Harald Sitter 2016-08-09 08:45:40 UTC
nevermind, still broken. won't be solved until plasma learns to clean up and our software learns to not crash in destructors.

[acheron]

Well even that is a bit out of date, as Harold and Jonathan are currently still trying to thrash this out and fix on #kde-neon on freenode irc.