Shutdown SIGKILLs processes

[Ben Giles]

When I use the indicator-applet-session to shutdown Gnome, any applications that are still running appear to be SIGKILL'd. Consequently when I next start a session various applications (eg, Google Chrome, Firefox) complain that they were not shutdown properly.

Wouldn't it be cleaner to send a SIGTERM to running processes to give them a chance to exit gracefully? If after a short period they're still running, then a SIGKILL can be sent.

I realise this can be solved by manually closing each open application. Do I have to shut them all down manually to get clean exits from them?

I'm using Karmic Koala.

[lavinog (lavinog)]

I think I noticed this while testing lucid.
I also noticed in lucid that the shutdown sound gets interrupted, which might be due to this issue.
I will check again if this was the case.

[pinzia (pinzia)]

maybe THE problem of this https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/562027?

[pinzia (pinzia)]

duplicate?https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/541368

[Chris Coulson (chrisccoulson)]

gnome-session only stops the processes that it knows about (ie, clients that register with it via XSMP or D-Bus), and it negotiates the shutdown of these processes via the session protocol. It doesn't kill them at all.

gnome-session doesn't touch the processes that didn't register with it (which I assume are the ones you have a problem with) - these processes likely just die when the X server goes away