[Bug 426556] Re: policykit cause high dbus-daemon cpu usage

[Esmaeil Nikfekr]

To troubleshoot high CPU usage caused by the dbus-daemon process, you can use the 
"$ dbus-monitor --session" 
command to monitor the messages being sent through dbus. If you notice a particular application sending a large number of messages to dbus-daemon, it may be the culprit. In my case, I discovered that my break taker app was sending lots of messages to dbus-daemon. After stopping it, the dbus-daemon CPU usage returned to normal. To identify if there is another app causing this issue, you can use the same command and observe if any message is frequently being sent or not.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/426556

Title:
  policykit cause high dbus-daemon cpu usage

Status in dbus package in Ubuntu:
  Invalid
Status in policykit package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: dbus

  When resuming from suspend, the system dbus-daemon (the one that runs
  as user messagebus) starts to run with 30%+ CPU usage. This started a
  couple of days ago (9/6/09). I can't find any particular reason that
  it does it besides that it appears to be triggered by resuming from
  suspend. The only way to get it back is to log out and restart dbus
  from the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/426556/+subscriptions