https://bugs.kde.org/show_bug.cgi?id=445862
--- Comment #2 from Dave Flogeras <[email protected]> --- I found a workaround, at least for my specific machine. It seems like on this machine, when I set up my konsole keyboard shortcut, I just assigned a key-combo to the shortcut under Session->Shortcuts->Custom Shortcuts->KMenuEdit->Konsole->Trigger. This shortcut I think is created by default. On other machines, I made a new custom group, then added a newly created shortcut by clicking edit->new->global shortcut->command/url and filling it in. What I notice is that if you go into /proc/`pidof ksmserver/fd and inspect the open files, starting console with the first shortcut does not seem to notify ksmserver of its presence, but using the "from scratch" shortcut seems to make a new socket to ksmserver for each konsole. I guess if konsole doesn't tell ksmserver about itself it cannot be queried for session management at logout. Not sure of the how or why, but it seems to fix/work around the issue here. I am also sure this used to work, and I only set the short cut up when I bought the laptop nearly three years ago. Hope it helps someone else get un-stuck. -- You are receiving this mail because: You are watching all bug changes.
