Bug 283879

Summary:	cannot shutdown kde session sometimes
Product:	[Unmaintained] ksmserver	Reporter:	Roman K. <roman.karlstetter>
Component:	general	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dirk.kde, jan, nate, ot.an, quazgar, stuffcorpse, s_chriscollins
Priority:	NOR
Version:	4.11.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roman K. 2011-10-12 20:36:32 UTC

Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

I cannot shutdown my kde session sometimes. I normally do this by clicking on the logout-plasmoid, but from time to time this doesn't work. Just nothing happens, as if I didn't click the button. 


Also, if I try to logout via commandline 

qdbus org.kde.ksmserver /KSMServer logout 0 2 2 

the same happens, i.e. nothing.



Reproducible: Sometimes

Steps to Reproduce:
try to logout/shutdown/reboot

Actual Results:  
nothing

Expected Results:  
logout/shutdown/reboot

I can only shutdown via "/sbin/shutdown" or "init 0" in these cases.

Comment 1 Dirk Tilger 2012-01-16 14:02:17 UTC

I'm using 4.7.4 and have that problem as well. It seems to be that in my case in KSMServer::completeShutdownOrCheckpoint a notification is created and its signal closed() is connected to the slot logoutSoundFinished(). However, this slot gets never called. I couldn't yet figure out what goes wrong, sending the event explicitely after connecting the slot to it didn't solve it.

I have a multicore AMD64 machine with damaged soundcard configuration (KDE thinks I have no soundcard).

Comment 2 Dirk Tilger 2012-01-16 14:09:26 UTC

I'm on Gentoo, btw. Oh, it seems I'm hitting bug 228005. This seems to be a fix: https://git.reviewboard.kde.org/r/103593/diff/.

Comment 3 Oswald Buddenhagen 2012-05-27 14:11:04 UTC

i'm seeing this problem as well. luckily, i use suspend to ram most of the time, so it doesn't bother me that much that the only way to exit a kde session is by crashing it.

Comment 4 Oswald Buddenhagen 2012-05-27 17:34:23 UTC

the problem is that ksmserver never considers the session fully started.

this is probably related to a "sorry" box telling me it could not start a .desktop file in Autostart (which worked just fine a while ago), and possibly knotify non-stop spamming me with an unidentified signal (there is just an annoying sound, no useful output; debug output is useless as well).

Comment 5 quazgar 2013-06-04 22:26:27 UTC

I can reproduce the original problem in 4.10.2 sometimes, but it's not reliably reproduceable. I think I should note that trying to invoke the logout process manually with

qdbus org.kde.ksmserver /KSMServer logout 0 2 2

does not produce any output in ~/.xsession-errors at all.

Comment 6 Roman K. 2013-06-04 22:31:35 UTC

That's right, it happened to me too in the last time (4.10.3). I use "systemctl poweroff" in these cases, but I don't think the KDE session is shut down properly then.

Comment 7 Nate Graham 2023-05-17 15:56:20 UTC

This issue has almost certainly been fixed at some point in the last 10 years. Any new occurrences of it would be a new issue with a new root cause that needs a new bug report.