https://bugs.kde.org/show_bug.cgi?id=486904
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|REPORTED |RESOLVED
--- Comment #11 from Nate Graham <n...@kde.org> ---
ksmserver performs cleanup and informs apps that a session-ending action has
been requested, so I'm not surprised that killing it is faster, because it
means that none of that happens. It also means that any app with unsaved
changes dies immediately, destroying your work. Hence why it exists. :)
So here's what's going on: when there's a delay like the one you're describing,
it means one or more apps are taking a long time to respond. Steam is a common
culprit. Ultimately there's nothing we can do about that, though we can do
better about communicating the cause for the delay to the user. I'm marking
this as a duplicate of the Bugzilla ticket tracking that request.
*** This bug has been marked as a duplicate of bug 188476 ***
--
You are receiving this mail because:
You are watching all bug changes.
