Hi,
I don't think this is a gnome bug.
Gnome doesn't force any application to quit, it just sends a "TERM"
signal (kill $PID), which is a nice kill.
After 5 seconds if an application is still running, it displays a window
: "following applications are still running", with 3 choices, "quit
anyway", "lock screen", or "cancel".
If you choose "quit anyway", it sends a "KILL" signal : kill -9 $PID.
I think amarok should catch the TERM signal and quit properly, but i am
not a developper and dont know if this is possible?
Quentin
Harald Sitter a écrit :
> Hm, more of a GNOME bug. It shouldn't kill $application but send a QUIT
> signal, then if the app doesn't quit within e.g. 5 seconds it can kill
> it. Just killing it is kind of rude ;-)
>
> Are the other affected people also running GNOME?
>
> ** Changed in: amarok (Ubuntu)
> Status: New => Incomplete
>
>
Hi,
I don't think this is a gnome bug.
Gnome doesn't force any application to quit, it just sends a "TERM"
signal (kill $PID), which is a nice kill.
After 5 seconds if an application is still running, it displays a window
: "following applications are still running", with 3 choices, "quit
anyway", "lock screen", or "cancel".
If you choose "quit anyway", it sends a "KILL" signal : kill -9 $PID.
I think amarok should catch the TERM signal and quit properly, but i am
not a developper and dont know if this is possible?
Quentin
Harald Sitter a écrit :
> Hm, more of a GNOME bug. It shouldn't kill $application but send a QUIT
> signal, then if the app doesn't quit within e.g. 5 seconds it can kill
> it. Just killing it is kind of rude ;-)
>
> Are the other affected people also running GNOME?
>
> ** Changed in: amarok (Ubuntu)
> Status: New => Incomplete
>
>