Hi all,
I'm still working on my problem with hundreds of zombie dbus-daemons. I guess it isn't that common of an issue.
After some investigation, I have found that the main culprit seems to be konsole(1). I mostly use my system in command-line mode and am constantly creating and killing konsoles for various jobs.
For some reason, creating a konsole forks a dbus-daemon (like this output from ps -ef):
walker 12859 1 0 Jul08 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
When the konsole terminal is killed, the daemon never goes away. My system performance gradually goes downhill and eventually I get a "no more system file descriptor" error as the number of daemons pile up.
Any suggestions for how to debug or fix this? Killing the dbus-daemons locks the window system. Should I take off the fork option in the dbus config file? Is there some way I can start konsoles so that they do a better job of reaping dbus-daemons?
kind regards -- Rick Walker
Rick Walker writes:
Hi all,
I'm still working on my problem with hundreds of zombie dbus-daemons. I guess it isn't that common of an issue.....
For some reason, creating a konsole forks a dbus-daemon (like this output from ps -ef):
walker 12859 1 0 Jul08 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sessionWhen the konsole terminal is killed, the daemon never goes away. My system performance gradually goes downhill and eventually I get a "no more system file descriptor" error as the number of daemons pile up.
First, this sounds like a bug and a rather nasty one at that. Second, do other terminal emulators exhibit this behavior?
On 07/10/14 06:51, Rick Walker wrote:
Hi all,
I'm still working on my problem with hundreds of zombie dbus-daemons. I guess it isn't that common of an issue.
After some investigation, I have found that the main culprit seems to be konsole(1). I mostly use my system in command-line mode and am constantly creating and killing konsoles for various jobs.
For some reason, creating a konsole forks a dbus-daemon (like this output from ps -ef):
walker 12859 1 0 Jul08 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sessionWhen the konsole terminal is killed, the daemon never goes away. My system performance gradually goes downhill and eventually I get a "no more system file descriptor" error as the number of daemons pile up.
Any suggestions for how to debug or fix this? Killing the dbus-daemons locks the window system. Should I take off the fork option in the dbus config file? Is there some way I can start konsoles so that they do a better job of reaping dbus-daemons?
I'm running kdm for my display manager and use KDE as my desktop. I've ssh'd into the system before logging in and I see....
[egreshko@f20f ~]$ ps -eaf | grep dbus-daemon dbus 638 1 0 Jul09 ? 00:00:06 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
after login and KDE desktop with no konsole started....
dbus 638 1 0 Jul09 ? 00:00:06 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation egreshko 7131 1 0 08:46 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session egreshko 7707 7699 0 08:46 ? 00:00:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
I then started 10 "copies" of konsole from the "Application Launcher". But, I still only get....
[egreshko@f20f ~]$ ps -aux | grep konsole egreshko 8180 0.5 5.4 682800 69572 ? Sl 08:54 0:01 /usr/bin/konsole
and
[egreshko@f20f ~]$ ps -eaf | grep dbus-dae dbus 638 1 0 Jul09 ? 00:00:06 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation egreshko 7131 1 0 08:46 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session egreshko 7707 7699 0 08:46 ? 00:00:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
-
David Benfell -
Ed Greshko -
Rick Walker