Bug 555795 - gnome-session fails to shut applications down
gnome-session fails to shut applications down
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: gnome-session
2.24.x
Other Linux
: Normal major
: ---
Assigned To: Session Maintainers
Session Maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2008-10-10 14:15 UTC by Martin Soto
Modified: 2009-03-25 01:42 UTC (History)
1 user (show)

See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Output of gnome-session --debug (90.39 KB, text/plain)
2008-10-10 14:18 UTC, Martin Soto
Details
The .xsession file used for the session (92 bytes, text/plain)
2008-10-10 14:19 UTC, Martin Soto
Details

Description Martin Soto 2008-10-10 14:15:14 UTC
While running gnome-session 2.24 under Ubuntu Intrepid beta, I noticed that some applications aren't being shut down when ending the session. Notable examples are Firefox, gnome-terminal and OpenOffice but a number of the programs normally started by the session also seem to be affected. I tried recompiling the Ubuntu package and deactivating all patches except those affecting the build system, but the problem didn't go away.

I'm attaching a log file that I obtained by running gnome-session with the --debug flag. It looks to me that gnome-session believes that all programs terminated normally and terminates itself. The programs, however, are still running and die only because their connection to the X server gets broken. The messages at the end of the log show this. I'm rating this bug as major since it can potentially cause user data loss.
Comment 1 Martin Soto 2008-10-10 14:18:11 UTC
Created attachment 120338 [details]
Output of gnome-session --debug
Comment 2 Martin Soto 2008-10-10 14:19:53 UTC
Created attachment 120339 [details]
The .xsession file used for the session

Just in case this is useful...
Comment 3 Vincent Untz 2009-03-25 01:42:38 UTC
I fixed this in trunk. 2.26.1 should have the fix. We were not sending the Die message to xsmp clients...

Note You need to log in before you can comment on or make changes to this bug.