I believe I just experienced this bug on a SuSE Linux 11.4 system. (kernel-desktop-2.6.37.6-0.7.1.x86_64) It is quite intermittent. I believe you should check the number of open file handles ( lsof | wc -l ) and also compare the open file handle count you get as root vs the number you get as an unprivileged user. On my system, that difference swells to 20,000 to 25,000 vs a normal number of 3,000 to 5,000 when DBus process is not consuming 100% CPU. What my gut tells me is happening is that something attached to the DBus -- and probably running at root privilege -- cannot get a file handle for whatever reason and goes into robo attempt to open another file handle mode. It may turn out that the actual problem is some common component to several packages. I cannot prove this because I did not see it. I would watch both the absolute number of file handles when DBus goes pathological (60,000 to 75,000 on my system) and the difference. I would also watch the number of open processes ( ps -ef | wc -l ). For whatever it is worth.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680444 Title: dbus-daemon eats 100% cpu and is not responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/680444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
