[Bug 229632] New: GNOME leaves stale processes after user logs out
https://bugzilla.novell.com/show_bug.cgi?id=229632 Summary: GNOME leaves stale processes after user logs out Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: marko.kolar@guest.arnes.si QAContact: qa@suse.de GNOME fails to clean up some processes after the user logs out. Among these are: - dbus-daemon - gnome-vfs-daemon - bonobo-activation-server - beagled - gpg-agent This not only wastes resources, but can also cause strange problems when the user logs back in. For example, a stale bonobo-activation-server will cause many programs under the control panel (e.g. gnome-keyboard-preferences) to throw an error: "Unable to start the settings manager 'gnome-settings-daemon'. Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 plaugraud@a1.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |plaugraud@a1.net ------- Comment #1 from plaugraud@a1.net 2007-01-26 11:04 MST ------- I detected the same or similar behavior, if I loged in to the KDE desktop. After log out, the process 'dbus-daemon' is still running (state is sleeping) as the user loged in before. By and by, more and more sleeping dbus-daemon are running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 jan@houtsma.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan@houtsma.net ------- Comment #2 from jan@houtsma.net 2007-02-01 07:59 MST ------- This annoys me as well. Using Fedora Core 6 here with Gnome 2.16. For every user that logs in and out the dbus-daemon and gnome-vfs-daemon remain in the processlist. After a month i have hundereds of these processes in ps!! In fedora it's launched from xinitrc(-common) as follows: [ -x /usr/bin/dbus-launch -a -z "$DBUS_SESSION_BUS_ADDRESS" ] && DBUS_LAUNCH="/usr/bin/dbus-launch --exit-with-session" but is NOT killed at logout!! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 ------- Comment #3 from jan@houtsma.net 2007-02-02 01:42 MST ------- John (J5) Palmieri wrote:
On Thu, 2007-02-01 at 17:34 +0100, Jan Houtsma wrote:
Havoc Pennington wrote:
Jan Houtsma wrote:
From what i can tell in fedora it's launched from xinitrc(-common) as follows:
[ -x /usr/bin/dbus-launch -a -z "$DBUS_SESSION_BUS_ADDRESS" ] && DBUS_LAUNCH="/usr/bin/dbus-launch --exit-with-session"
Are you sure the session bus is the one that's leaked?
http://lists.freedesktop.org/archives/dbus/2006-December/006662.html
In some "su" type situations, a new bus can be started automatically. These situations are more likely to cause bus leaks. You might see if just logging in as a user and logging out leaks a daemon, or if you have to do something more.
I see the following (remotely logged in from another terminal):
All clear. No processes. Before the Gnome login: --------------------------------------------------
root:/etc/X11/xinit> ps -ef|grep dbus dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system root 24040 24021 0 17:21 pts/1 00:00:00 grep dbus
Now login as via the Fedora Gnome Graphical interface as user 'jan' and immideliatelly logging out again back to the Gnome login screen: -----------------------------------------------------------------------------------------------------------------------------------------
root:/etc/X11/xinit> ps -ef|grep dbus dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system jan 24134 1 0 17:23 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
root:/etc/X11/xinit> ps -ef|grep jan jan 24134 1 0 17:23 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session jan 24179 1 0 17:23 ? 00:00:00 /usr/libexec/gnome-vfs-daemon
I have had other people report this but I can not reproduce it other than trying to run an app that uses gnome-vfs within a shell which does not have the DBUS_SESSION_BUS_ADDRESS set. It is interesting that you have no associated dbus-launch. Can you do me a favor and do the same operations as before but this time before you log out do a ps -ef|grep dbus so I can compare the pids.
Here you go. Now woth another user (ramon). B.t.w. the system is completely up2date to the latest updates. I did 4 things here: 1. Before login to X: ps -ef|grep -E 'ramon|dbus' 2. During the login: ps -ef|grep -E 'ramon|dbus' followed by only ps -ef|grep -E 'ramon|dbus' 3. After logout: ps -ef|grep -E 'ramon|dbus' root:/etc/X11/xinit> rpm -qa|grep dbus dbus-devel-1.0.1-9.fc6 dbus-glib-0.70-6.fc6 dbus-x11-1.0.1-9.fc6 dbus-glib-devel-0.70-6.fc6 dbus-1.0.1-9.fc6 dbus-sharp-0.63-6.fc6 dbus-python-0.70-6 # BEFORE LOGIN root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system # DURING LOGIN root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system ramon 27092 2681 0 08:28 ? 00:00:00 -/bin/zsh -c /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27136 27092 0 08:28 ? 00:00:00 /usr/bin/gnome-session ramon 27137 27136 0 08:28 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27140 1 0 08:28 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27141 1 0 08:28 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ramon 27147 1 4 08:28 ? 00:00:00 /usr/libexec/gconfd-2 5 ramon 27150 1 0 08:28 ? 00:00:00 /usr/bin/gnome-keyring-daemon ramon 27152 1 0 08:28 ? 00:00:00 /usr/libexec/gnome-settings-daemon ramon 27164 27152 0 08:28 ? 00:00:00 [xrdb] <defunct> ramon 27166 27152 0 08:28 ? 00:00:00 [xrdb] <defunct> ramon 27171 1 0 08:28 ? 00:00:00 metacity --sm-client-id=default1 ramon 27175 1 1 08:28 ? 00:00:00 gnome-panel --sm-client-id default2 ramon 27177 1 4 08:28 ? 00:00:00 nautilus --no-default-window --sm-client-id default3 ramon 27181 1 1 08:28 ? 00:00:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=16 ramon 27184 1 0 08:28 ? 00:00:00 /usr/libexec/gnome-vfs-daemon ramon 27188 1 0 08:28 ? 00:00:00 eggcups --sm-client-id default4 ramon 27190 1 0 08:28 ? 00:00:00 bluetooth-applet ramon 27196 1 0 08:28 ? 00:00:00 gnome-volume-manager --sm-client-id default5 ramon 27199 1 1 08:28 ? 00:00:00 /usr/bin/python -tt /usr/bin/puplet ramon 27206 1 0 08:28 ? 00:00:00 nm-applet --sm-disable ramon 27212 1 0 08:28 ? 00:00:00 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=19 ramon 27214 1 0 08:28 ? 00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=22 ramon 27221 1 0 08:28 ? 00:00:00 /usr/libexec/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=25 ramon 27223 1 0 08:28 ? 00:00:00 /usr/libexec/geyes_applet2 --oaf-activate-iid=OAFIID:GNOME_GeyesApplet_Factory --oaf-ior-fd=31 ramon 27227 1 0 08:28 ? 00:00:00 /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=36 ramon 27229 1 0 08:28 ? 00:00:00 /usr/libexec/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=39 ramon 27232 1 0 08:28 ? 00:00:00 pam-panel-icon --sm-client-id default0 ramon 27247 1 0 08:28 ? 00:00:00 /usr/libexec/mapping-daemon root 27249 26550 0 08:28 pts/1 00:00:00 grep -E ramon|dbus root:/etc/X11/xinit> ps -ef|grep -E 'dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system ramon 27092 2681 0 08:28 ? 00:00:00 -/bin/zsh -c /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27137 27136 0 08:28 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27140 1 0 08:28 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27141 1 0 08:28 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 27251 26550 0 08:28 pts/1 00:00:00 grep -E dbus # AFTER LOGOUT root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system ramon 27141 1 0 08:28 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ramon 27184 1 0 08:28 ? 00:00:00 /usr/libexec/gnome-vfs-daemon root 27308 26550 0 08:29 pts/1 00:00:00 grep -E ramon|dbus I see two dbus-launch lines in the ps list during login. Has that anything to do with this? I have no idea why two? Is the latter entry the result of the one above it with the /bin/zsh in front of it? Is it caused maybe by the fact the users default shell is /bin/zsh alltogether??? And i couldn't resist to try... And that seems to be related indeed!!! Now with users default shell is /bin/bash (in /etc/passwd): # BEFORE LOGIN root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system root 27323 26550 0 08:44 pts/1 00:00:00 grep -E ramon|dbus # DURING LOGIN root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system ramon 27327 2681 1 08:45 ? 00:00:00 /usr/bin/gnome-session ramon 27378 27327 0 08:45 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27381 1 0 08:45 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ramon 27382 1 0 08:45 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients ramon 27388 1 5 08:45 ? 00:00:00 /usr/libexec/gconfd-2 5 ramon 27391 1 0 08:45 ? 00:00:00 /usr/bin/gnome-keyring-daemon ramon 27393 1 1 08:45 ? 00:00:00 /usr/libexec/gnome-settings-daemon ramon 27405 27393 0 08:45 ? 00:00:00 [xrdb] <defunct> ramon 27407 27393 0 08:45 ? 00:00:00 [xrdb] <defunct> ramon 27409 1 0 08:45 ? 00:00:00 metacity --sm-client-id=default1 ramon 27416 1 1 08:45 ? 00:00:00 gnome-panel --sm-client-id default2 ramon 27418 1 4 08:45 ? 00:00:00 nautilus --no-default-window --sm-client-id default3 ramon 27422 1 0 08:45 ? 00:00:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=16 ramon 27425 1 0 08:45 ? 00:00:00 eggcups --sm-client-id default4 ramon 27427 1 0 08:45 ? 00:00:00 bluetooth-applet ramon 27431 1 1 08:45 ? 00:00:00 /usr/bin/python -tt /usr/bin/puplet ramon 27433 1 0 08:45 ? 00:00:00 nm-applet --sm-disable ramon 27435 1 0 08:45 ? 00:00:00 /usr/libexec/gnome-vfs-daemon ramon 27438 1 0 08:45 ? 00:00:00 gnome-volume-manager --sm-client-id default5 ramon 27443 1 0 08:45 ? 00:00:00 pam-panel-icon --sm-client-id default0 ramon 27476 1 0 08:45 ? 00:00:00 /usr/libexec/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=25 ramon 27478 1 0 08:45 ? 00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=31 ramon 27480 1 0 08:45 ? 00:00:00 /usr/libexec/geyes_applet2 --oaf-activate-iid=OAFIID:GNOME_GeyesApplet_Factory --oaf-ior-fd=34 ramon 27483 1 0 08:45 ? 00:00:00 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=19 ramon 27488 1 0 08:45 ? 00:00:00 /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=24 ramon 27490 1 0 08:45 ? 00:00:00 /usr/libexec/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=45 ramon 27499 1 0 08:45 ? 00:00:00 /usr/libexec/mapping-daemon # AFTER LOGIN root:/etc/X11/xinit> ps -ef|grep -E 'ramon|dbus' dbus 2243 1 0 Jan19 ? 00:00:02 dbus-daemon --system So it's /bin/zsh inside /etc/passwd which is causing this. Guess with zsh the dbus process doesn't "see" the session or shell exiting or something? On this (development) system zsh is the default for users. Preferably wish to keep it that way. Anyway getting closer to the root cause.... -- jan _______________________________________________ dbus mailing list dbus@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dbus -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |hvogel@novell.com ------- Comment #4 from jpr@novell.com 2007-02-14 13:27 MST ------- What do you think of comment #3 regarding zsh? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 ------- Comment #5 from jan@houtsma.net 2007-02-14 15:19 MST ------- (In reply to comment #4)
What do you think of comment #3 regarding zsh?
Also see here: https://bugs.freedesktop.org/show_bug.cgi?id=9884 Changed default shell from /bin/zsh into /bin/bash, and no problem since. However it should work with zsh as well. Didn't test it with ksh b.t.w. Regards, Jan Houtsma -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 hvogel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|hvogel@novell.com | ------- Comment #6 from hvogel@novell.com 2007-02-15 04:53 MST ------- i dont know what i can do in zsh here, its clearly a problem with dbus. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 ------- Comment #7 from jan@houtsma.net 2007-02-15 06:27 MST ------- I agree although i didn't open this mr. I only added some more info and references. I think this one should depend on the dbus one (which hides in the freedesktop bugzilla). Reference is above in this report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |thoenig@novell.com |gnome@forge.provo.novell.com| -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 thoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|thoenig@novell.com |bnc-team-gnome@forge.provo.novell.com ------- Comment #8 from thoenig@novell.com 2007-02-16 05:32 MST ------- That is a session problem (here: GNOME). The D-Bus session daemon will exit properly if the session was shut down properly. As there are still processes running which belong to the (already closed) session this does not happen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 ------- Comment #9 from jan@houtsma.net 2007-02-16 06:21 MST ------- Well, maybe. But one thing is sure. As soon as i change the users default shell from /bin/zsh into /bin/bash the problem disappears. I think dbus somehow looks to shell exit status or something when X closes. It doesn't see the zsh exiting and thus the process is not killed. If i change to bash (which is the default when you don;t change the users shell) dbus notices the shell exiting when X exits and also closes down dbus. It doesn;t do that with other shells than bash. I think dbus should check X11 exiting (user logs out) and not look at the shell. And if it does look at the shell it should also work for zsh (and possibly others as well). I created the bug report in bugzilla as you can see above and think Novell should vote there to get a fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 felix.rommel@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix.rommel@web.de ------- Comment #11 from felix.rommel@web.de 2007-03-11 03:51 MST ------- Reply to comment #9: The error described in this bug report also happens if the default shell is /bin/bash! After a default installation I log in a Gnome session as normal user (default shell: bash) and if I exit there are still some Gnome processes in memory: felix 3744 0.0 0.1 3776 912 ? Ss 13:11 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session felix 3793 0.0 0.5 9432 3820 ? S 13:11 0:00 /opt/gnome/sbin/gnome-vfs-daemon felix 4604 0.0 0.1 3772 904 ? Ss 13:28 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session felix 4657 0.0 0.5 9432 3824 ? S 13:28 0:00 /opt/gnome/sbin/gnome-vfs-daemon felix 5580 0.0 0.1 3776 896 ? Ss 13:49 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session felix 5627 0.0 0.5 9260 3684 ? S 13:49 0:00 /opt/gnome/sbin/gnome-vfs-daemon root 5908 0.0 0.0 1952 648 tty1 S+ 13:54 0:00 grep felix -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 knweiss@science-computing.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knweiss@science-computing.de ------- Comment #12 from knweiss@science-computing.de 2007-05-08 06:32 MST ------- I can 100% reproduce this bug even with user root, bash and a KDE session: Each X login creates a new dbus-daemon session process even though there still exists the process from the old session (which wasn't terminated even though dbus was call with --exit-with-session). I'm no D-Bus export but I'm wondering how the dbus launch is supposed to work. This is from /etc/X11/xinit/xinitrc.common: # # Launch dbus if no session is activ or if the session is not reachable # if dbuslaunch="$(type -p dbus-launch)" && dbussend="$(type -p dbus-send)" ; then dbustest () { $dbussend --session --type=method_call \ --dest='org.freedesktop.DBus' \ /org/freedesktop/DBus \ org.freedesktop.DBus.NameHasOwner \ string:'org.freedesktop.DBus' > /dev/null 2>&1 } if test -z "$DBUS_SESSION_BUS_ADDRESS" || ! dbustest ; then WINDOWMANAGER="$dbuslaunch --sh-syntax --exit-with-session $WINDOWMANAGER" fi fi unset dbuslaunch dbussend dbustest Later on there finally is a "exec $WINDOWMANAGER". Question: How can DBUS_SESSION_BUS_ADDRESS here in this environment ever be NOT the empty string so that no new dbus session daemon gets launched during login? Please notice that the output of dbus-launch (which sets DBUS_SESSION_BUS_ADDRESS in sh syntax) is not evaluated. So is it a bug that the old dbus session daemon doesn't get terminated on logout or is it a bug that a new daemon gets started even though an old daemon still exists. Or both? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 thoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@novell.com Status|NEW |NEEDINFO Info Provider| |werner@novell.com ------- Comment #13 from thoenig@novell.com 2007-05-08 06:36 MST ------- Werner, if I recall correctly you worked on what is mentioned in comment #12. Can you please have a look? Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632 werner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|werner@novell.com | ------- Comment #14 from werner@novell.com 2007-05-08 07:16 MST ------- This test is for _sub_ sessions only, there was a bug report about sub sessions and failing processes therein. AFAIK there was never the intention to reuse an old dbus session due to the fact that the those sessions were closed in history. If this is not true anymore than similar way as for gpg in /etc/X11/xdm/sys.xsession has to be used to get the information into a doted file in the users home directory ... but then the dbuslaunch should run as a daemon ... nevertheless the option `--exit-with-session' should be close the dbus at the end of a session and therefore such a way should not be needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229632#c15
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=229632#c16
Toni Zimmer
https://bugzilla.novell.com/show_bug.cgi?id=229632#c17
--- Comment #17 from Toni Zimmer
https://bugzilla.novell.com/show_bug.cgi?id=229632#c18
--- Comment #18 from Felix Rommel
https://bugzilla.novell.com/show_bug.cgi?id=229632#c19
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=229632#c20
--- Comment #20 from Felix Rommel
https://bugzilla.novell.com/show_bug.cgi?id=229632#c21
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=229632#c22
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=229632#c23
Federico Mena Quintero
participants (1)
-
bugzilla_noreply＠novell.com