Okay, I suspect the Gtk problem is indeed a separate issue.

Can you try to determine if running any particular application (or performing any particular activity) seems to cause or help cause this to occur?
It could be an application is inhibiting certain actions, but not releasing those inhibits when it exits.

bcooksley wrote:Okay, I suspect the Gtk problem is indeed a separate issue.

It may be a separate issue, but it may also be indicative that something does not work --sometimes-- as expected at the core of KDE.

bcooksley wrote:Can you try to determine if running any particular application (or performing any particular activity) seems to cause or help cause this to occur?
It could be an application is inhibiting certain actions, but not releasing those inhibits when it exits.

I doubt it. When I suspect that I will not be able to logout (just upon login, by either noticing that Dolphin takes long to load the front tab contents, or by seeing that Firefox --the first application I usually launch-- has problems), I try to logout. Let me remind you that the only applications that are restored upon login are Dolphin and konsole, and dropbox at the tray.

Can you try enabling debug output of KSMServer (or even just all areas, although be aware this will cause increased disk usage) and then monitor ~/.xsession-errors when attempting to logout of a blocked session?

Debug output can be controlled through "kdebugdialog".

I know, this topic is a little older already, but I have the same problem (not the Firefox part, just the logout and shutdown buttons not working).
Is there any solution to this? It's quite annoying. I found a few bug reports about this issue on bko, but they are all from 2007, 2009 or 2010 and seem to not include any practical solution to the problem.

I tried the qdbus command suggested earlier in this thread, but it doesn't do anything. There are also no error or warning messages in either the system logs or .xsession-errors (all debug output enabled via kdebugdialog).

Would be great if someone could help me with this as it's not the first time I'm experiencing this issue.

Windows error?

The only thing I can suggest unfortunately is quitting/killing applications one by one until you find the one which is holding the session open. I haven't been able to find the exact cause of this issue unfortunately in the times i've tried to assist others in solving the issue.

I have the same issue. Logout/Shutdown buttons don't work. Also the command has no effect: qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout 0 0 0.

The only one clue I have is that it is unique to this user. Another user account on my system doesn't have this problem. Any ideas what .kde user config files I might find that affect logout/shutdown?

Please see your other topic - in particular please check ~/.xsession-errors for the previously mentioned error message.