registry team mailing list archive

Thread
Date

[Bug 534210] [NEW] Shutdown SIGKILLs processes

To: registry@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <534210@xxxxxxxxxxxxxxxxxx>
Date: Fri, 21 May 2010 22:58:46 -0000
Reply-to: Bug 534210 <534210@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

You have been subscribed to a public bug:

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.

** Affects: null
     Importance: Undecided
         Status: New

** Affects: gnome-session (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Shutdown SIGKILLs processes
https://bugs.edge.launchpad.net/bugs/534210
You received this bug notification because you are a member of Registry Administrators, which is the registrant for NULL Project.