Your message dated Sun, 22 Aug 2010 18:35:31 +0200
with message-id <1282494931.28162.37.ca...@localhost>
and subject line Re: gnome-session doesn't signal autostart jobs when session
ends: Actually... I was wrong
has caused the Debian Bug report #593961,
regarding gnome-session doesn't signal autostart jobs when session ends
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
593961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593961
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-session-bin
Severity: normal
Hi,
/usr/bin/gnome-session doesn't signal autostart jobs when the session
ends. Create for example an autostart job like this one:
$ cat > ~/.config/autostart/sleep.desktop <<EOF
> [Desktop Entry]
> Type=Application
> Name=Sleep
> Exec=sleep 3600
> EOF
After logout/login you can see that gnome-session has started the
previously created job and is registered as its parent process:
$ ps -C sleep -C x-session-manager -f
UID PID PPID C STIME TTY TIME CMD
1000 27714 27681 0 17:55 ? 00:00:00 x-session-manager
1000 27797 27714 0 17:55 ? 00:00:00 sleep 3600
However after logging out/logging in again the situation is like this:
$ ps -C sleep -C x-session-manager -f
UID PID PPID C STIME TTY TIME CMD
1000 27797 1 0 17:55 ? 00:00:00 sleep 3600
1000 28030 27997 1 17:58 ? 00:00:00 x-session-manager
1000 28111 28030 0 17:58 ? 00:00:00 sleep 3600
So instead of signaling (SIGHUP or SIGTERM) its children when the
session ends, gnome-session simply orphans them, leaving useless
processes around. Additionally it doesn't recognize that this particular
autostart job is already running when a new session is created, but just
creates a new one.
I think that gnome-session should at least SIGHUP its child processes
when the session ends.
Best regards
Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
tags 593961 wontfix
thanks
After rethinking the problem, I have come to the conclusion that the
current behaviour of gnome-session is correct and that my initial
suggestion is wrong. It is not gnome-session's responsibility to tell
the autostart jobs when they should terminate, since there may well be
valid reasons for such a job to continue running after the session has
ended. Consider this example:
Adam has set up an autostart job which automatically fetches his mails
when he logs in. One day his sister sends him some holiday pictures
which are quite big and take some time do download. A few minutes after
Adam has logged in and the downloading started, his wifes enters the
room and wants to print something. Adam logs off and his wife prints her
document. When Adam logs back on his sisters pictures just finished
downloading and he can look at them together with his wife.
I now think the jobs should decide for themselves when to exit and have
therefore closed the bug as `wontfix'. Feel free to reopen/untag if you
think differently!
Best regards
Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
--- End Message ---
