Bugzilla – Bug 158098
dbus-daemon does not end with users sessions and has many instances for each user
Last modified: 2007-06-05 09:58:04 UTC
My system runs LTSP for 60 users concurrently, and i have noticed that many dbus-daemon instances stays indefinitely even after logout. I am using xfce4 as the WindowManager, and the following process list has 8 users logged in, but the list comes with many more user processes: antocm@halworld:/etc/X11/xinit> ps -aef | grep dbus | sort | more 100 3903 1 0 Mar09 ? 00:00:01 /usr/bin/dbus-daemon --system 10157 19441 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10188 14615 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10188 6309 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10527 9355 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10531 24253 1 0 Mar10 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 10531 24255 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10615 22039 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10615 3520 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10662 15856 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10662 32422 1 0 09:11 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10662 992 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10675 1329 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10675 21035 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10675 4125 1 0 12:01 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10675 7872 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10913 21813 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session 10913 3882 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session amateus 11392 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session amateus 18664 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session amateus 20914 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session amateus 5842 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session amateus 8937 1 0 Mar09 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session antocm 13220 13130 0 21:28 pts/1 00:00:00 grep dbus ccruz 17870 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session dpisco 17999 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session dpisco 2138 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session dpisco 7014 1 0 Mar09 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session eramos 20176 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session eramos 714 1 0 09:15 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session festeves 20507 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session iduarte 12854 1 0 19:34 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session iduarte 12856 1 0 19:34 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 iduarte 6066 1 0 13:57 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jgil 20724 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jgil 28194 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 10795 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 17005 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 22650 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 2269 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 25826 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 30489 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session jrmoura 31027 1 0 09:01 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session lesteves 13507 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session lesteves 26936 1 0 Mar12 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session lesteves 28585 1 0 08:08 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session lesteves 30136 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 15204 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 24396 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 29396 1 0 08:25 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 31022 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 4524 1 0 12:15 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session luiss 5824 1 0 13:54 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mamaral 14937 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mfonseca 18703 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mjose 14401 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mjose 26634 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mmourato 16084 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mmourato 9773 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mpires 17339 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mserra 5479 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session mserra 5480 1 0 Mar13 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 pmartins 21067 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session pmatos 30666 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session pmatos 742 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session qneves 15452 1 0 Mar10 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session qneves 30111 1 0 08:56 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session qneves 31675 1 0 Mar13 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session qneves 922 1 0 09:16 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session
Apparently there is no major impact in having these processes.
Reassigning to the maintainer for a comment.
Antonio, are you fine with closing this one as you are not experiencing any impact?
I have impact, as dozens of processes take time, and they increase in number indefinitely. I have been studying it with more carefull, and i see that in the first place, only one dbus-daemon process exists. However, as i am using LTSP, and they encourage the users to just press the power button to stop the terminal, they do not always logout from X session. In that case, many processes stay open until the next login: bribeiro 1166 1 0 16:28 ? 00:00:00 xfce-mcs-manager bribeiro 1368 1 0 16:30 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session bribeiro 1387 1 0 16:30 ? 00:00:00 xfce-mcs-manager bribeiro 1774 1 0 16:34 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session bribeiro 1790 1 0 16:34 ? 00:00:00 xfce-mcs-manager bribeiro 2108 2085 0 16:46 ? 00:00:00 /bin/sh /home/perfil2/.config//xfce4/xinitrc bribeiro 2195 2108 0 16:46 ? 00:00:00 ssh-agent /etc/X11/xinit/xinitrc bribeiro 2209 1 0 16:46 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 bribeiro 2211 1 0 16:46 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session bribeiro 2222 2108 0 16:46 ? 00:00:00 /bin/sh /home/perfil2/.config//xfce4/xinitrc bribeiro 2223 2222 0 16:46 ? 00:00:00 xscreensaver -no-splash bribeiro 2226 2108 3 16:46 ? 00:00:02 /usr/bin/xfce4-session bribeiro 2229 1 0 16:46 ? 00:00:00 xfce-mcs-manager bribeiro 2232 1 0 16:46 ? 00:00:00 xfwm4 bribeiro 2236 1 1 16:46 ? 00:00:00 xfce4-panel bribeiro 2240 1 0 16:47 ? 00:00:00 xftaskbar4 bribeiro 2242 1 1 16:47 ? 00:00:00 xfdesktop Once the user login again, every process recycles, except for: bribeiro 1166 1 0 16:28 ? 00:00:00 xfce-mcs-manager bribeiro 1368 1 0 16:30 ? 00:00:00 dbus-daemon --fork --print-pid 9 --print-address 7 --session If the user now logs out correctly, every process closes correctly except for these ones. If you think that dbus-daemon process is acting normal, please close the bug. Is there any chance to check for previous dbus-daemon processes when a user starts a session? in that case it would reuse the already created process of dbus-daemon, or even close this before oppening another.
As it is fixed in newer versions we'll close the bug. We will not deliver an online-update for 10.0 fro this bug, sorry.