Package: gnome-session Version: 2.22.3-2 --- Please enter the report below this line. ---
I think I found a related bug on my system just a few days ago. I had just set gnome-session-properties to "save session = enabled" for a while. After a few reboots I went to disable it as it didn't meet my needs. To my surprise I found out that I'm running ten instances of seahorse-agent with different sm-config-prefix options. Seahorse-agent didn't have the parameter --sm-disable. I disabled the instances by saving a session where I killed them. Though I think the instances shouldn't have been there in the first place. The other programs that had --sm-disable didn't save to the session and start multiple instances anymore. So if thats the only case this issue is tracking it can probably be closed. Though gnome-session should probably still have a bug on saved sessions as the above behaviour isn't what people want. --- System information. --- Architecture: i386 Kernel: Linux 2.6.28.4 Debian Release: 5.0 500 unstable ftp.sunet.se 500 unstable ftp.funet.fi 500 unstable ftp.fi.debian.org --- Package information. --- Depends (Version) | Installed ========================================-+-=============== libatk1.0-0 (>= 1.20.0) | 1.22.0-1 libbonobo2-0 (>= 2.15.0) | 2.22.0-1 libc6 (>= 2.7-1) | 2.7-18 libdbus-1-3 (>= 1.0.2) | 1.2.1-5 libdbus-glib-1-2 (>= 0.71) | 0.76-1 libgconf2-4 (>= 2.13.5) | 2.22.0-1 libglib2.0-0 (>= 2.16.0) | 2.16.6-1 libgnome-keyring0 (>= 2.22.0) | 2.22.3-2 libgnome2-0 (>= 2.17.3) | 2.20.1.1-2 libgnomeui-0 (>= 2.17.1) | 2.20.1.1-2 libgtk2.0-0 (>= 2.12.0) | 2.12.11-4 libice6 (>= 1:1.0.0) | 2:1.0.4-1 liborbit2 (>= 1:2.14.10) | 1:2.14.16-0.1 libpango1.0-0 (>= 1.20.3) | 1.20.5-3 libsm6 | 2:1.0.3-2 libwrap0 (>= 7.6-4~) | 7.6.q-16 libx11-6 | 2:1.1.5-2 libxau6 | 1:1.0.3-3 gconf2 (>= 2.12.1-1) | 2.22.0-1 gnome-control-center (>= 1:2.22) | 1:2.22.2.1-2 gnome-settings-daemon | 2.22.2.1-2
signature.asc
Description: Digitaalisesti allekirjoitettu viestin osa
