> This info should be posted on the bug report, as it provided
> me with a potentially important clue.

Yeah, I figured this discovery might lead somewhere. :)

I posted the same text to the bug report when I sent the email. :) At that time I also updated bug reports 258 and 681 with references to 922.

> What happens if you rename the krootbacking executable to
> something else so that it cannot be executed by ksmserver, and set
> showFancyLogout=true? Does the logout progress at the faster speed?

I don't know what krootbacking is. Typing krootbacking --help provided some hint. As soon as I saw the word xscreensaver my hair bristled and ears twitched.

I have the package installed but never, ever use xscreensaver.

I tested what you asked: krootbacking-> krootbacking.old and edited showFancyLogout=true. I opened kate, changed the file and selected the logout applet button. The non modal feedback "Saving your settings" dialog appeared and no dialog from kate to save the file. However, this time when I pressed Ctrl-Alt-Backspace to escape the hang, as the screen repainted I saw the outline of the kate dialog asking me whether I wanted to save or abort. I don't recall ever seeing that before when pressing Ctrl-Alt-Backspace during these tests.

So I tried again, this time blindly pressing Alt-D (&Do not save) and Alt-A (&Abort closing). Neither attempt succeeded and I pressed Ctrl-Alt-Backspace to escape. Other than the expected "client killed" messages I saw nothing helpful in the xsession log.

I do not use any wallpaper. I don't know whether that makes a difference but I saw that in the krootbacking sources.

With krootbacking still renamed, restoring showFancyLogout=false restored the save mechanism when logging out.

With that said, does any of this have to do with bug report 760, "TDE exits too slow"?

Darrell