GNOME Bugzilla – Bug 344476
"gnome-session-save --kill" saves the session instead of killing it
Last modified: 2007-04-02 15:47:16 UTC
When I issue the command "gnome-session-save --kill", I get a "Your session has been saved" dialog. If I then issue the same command again, it kills my session as I expect it would already the first time. I've had this error a fairly long time; it's not new in 2.14. Possibly related: I use sawfish as WM.
Does this still happen with 2.16? The code looks like it should not pop up that dialog if --kill is given. So the fact that it appears is interesting...
Yes it still happens in 2.16. Not always bug every now and then...
I think there's a correlation between the Skype client (downloadable from skype.com) and this problem. It runs in the background and adds an icon to the notification area. I never see the error when I haven't started this application, but I often (possibly always) get it otherwise.
Is it actually saving the session? That is, does it create a new ~/.gnome2/session file? I've noticed that if an application cancels the logout (eg, start gedit, type some random characters, try to log out, and then click "Cancel Logout" in the dialog that gedit pops up), then gnome-session pops up the "your application has been saved" dialog, although it does not actually save the session. So it might be that skype is silently cancelling the logout.
It doesn't update the ~/.gnome2/session file for me when this occurs.
This bug still exists for Gnome 2.18. But now skype just cancel the logout, the "Your session is saved" dialog is gone... but it is still annoying.
If the dialog is gone, then the (gnome-session) bug is fixed. Skype is explicitly telling gnome-session that you have decided that you don't want to log out; gnome-session has no way to know that it's lying. (Probably the intent was that you don't want to be logged out *if a call is in progress*, but they were just overzealous, or else maybe there's a bug in their code and they forgot to test the no-call-in-progress case. You could try filing a bug against skype.)