On Tue, 14 Jun 2011 at 15:39:37 +0100, Simon McVittie wrote:
> On Fri, 10 Jun 2011 at 11:53:55 +0400, Alexandr Bravo wrote:
> > After last update of dbus for amd64 testing "dbus-daemon --system" consumes
> > about 40% of CPU, which is not normal I think.
>
> Can you get strace output or a stack trace from the faulty dbus-daemon
> to see what it's up to, similar to on
> <https://bugzilla.redhat.com/show_bug.cgi?id=667787>?
>
> If you look in /proc/PID/fd (for the pid of the faulty dbus-daemon), does
> it have a large number (hundreds) of file descriptors?
>
> Do you use KDE? That Red Hat bug involves a KDE process that leaks D-Bus
> connections.
Does this bug still appear? If it does, we'll need some more information
(see above) to make any progress on fixing it.
> There is also a D-Bus bug where dbus-daemon can busy-loop if it is watching
> too many file descriptors
This was fixed in D-Bus 1.5.x, so the versions in testing/unstable (1.6.x)
no longer have that bug. This might solve what you were seeing?
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
