I found out what is causing dbus to go nuts. It's part of policykit,
/usr/lib/policykit/polkit-read-auth-helper.
I found out by simple killing processes and daemons one at a time until
dbus stopped freaking out. I guess I'll go talk to the policykit guys
now. Is there some way to transfer this bug
How do I find out what is doing that, then?
--
dbus-daemon high cpu usage after resume from suspend
https://bugs.launchpad.net/bugs/426556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
On Sat, 2009-10-10 at 22:55 +, Joshua Gardner wrote:
> I asked on the forums here
> http://ubuntuforums.org/showthread.php?t=1275316 but now response so
> far. This thread includes a dump from dbus-monitor --system (attached
> here too) for a few seconds which shows large amounts of spam appar
Still does it, mostly after resume from suspend but sometimes on its
own.
I asked on the forums here
http://ubuntuforums.org/showthread.php?t=1275316 but now response so
far. This thread includes a dump from dbus-monitor --system (attached
here too) for a few seconds which shows large amounts of s
How did that go?
Often high D-Bus CPU usage is actually due to a process spamming the bus
with a large number of messages
** Changed in: dbus (Ubuntu)
Status: New => Incomplete
--
dbus-daemon high cpu usage after resume from suspend
https://bugs.launchpad.net/bugs/426556
You received thi
Never mind, it seems it has nothing to do with resuming from suspend.
This morning it started doing it about half an hour after starting my
laptop.
It's too soon to call but I think it had something to do with my messing
with some more esoteric settings for nautilus in gconf. I've reset
nautilus a
