Bug#593961: gnome-session doesn't signal autostart jobs when session ends

Alexander Kurtz kurtz.alex at googlemail.com
Sun Aug 22 16:20:33 UTC 2010


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



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20100822/07ae72c6/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list