High dbus cpu utilization

[Tom]

It appears that dbus-daemon is occupying a lot of cpu resource. By running dbus-monitor as my local non-root user, i can see hundreds of the same message repeated every second second (see below)

method call sender=:1.87201 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=167940 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.87201"
   string ":1.87201"
   string ""

I've tried tracking back the sender id, however I cant seem to get the name of the process that's spamming dbus.

By running:
tom@valhalla:~$ dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID string::1.87201

I get the error:
Error org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ':1.57837': no such name

Maybe this is related to the NameOwnerChanged member? I don't really know enough about dbus, so I can't say whats causing this.

Over a period of half an hour, this can cause all of the cpu resource to be maxed forcing a reboot.

ProblemType: Bug
DistroRelease: elementary OS 0.3
Package: elementary-desktop 1.348+392~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashDB: elementary_meta
CurrentDesktop: Pantheon
Date: Mon Aug 11 18:30:16 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-11 (0 days ago)
InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: elementary-meta
SuspiciousXErrors: [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)

[Tom (thehorrorthehorror)]

This appears to have been fixed with the new round of updates that came in this morning. I'm no longer seeing a large amount of messages on dbus. : )

Please close this issue.

[J. Antonio Romero (nsdragon)]

I just started seeing this issue as well, down to the constant message spam in dbus-monitor, just as described in the bug description. Absolutely no idea what's been causing this.

[Devon Berkenstock (lhy19)]

I had been wondering what was causing my CPU usage to be so high. It doesn't show up as using that much in top or htop.

[Devon Berkenstock (lhy19)]

I had been wondering what was causing my CPU usage to be so high. It doesn't show up as using that much in top or htop.

[Colin O'Brien (insanitybit)]

I have this issue as well, installed the image today and it's all fully updated.

[Albert (albert-reig)]

Same problem, see attached file.

[Maarten Verwijs (x-contact-0)]

+1

Same problem after a fresh install on a Macbook Air mid-2013.

[Maarten Verwijs (x-contact-0)]

> Same problem after a fresh install on a Macbook Air mid-2013.

Fresh and fully upgraded, obviously...

[J. Antonio Romero (nsdragon)]

I just found that I can consistently make dbus-daemon go crazy when I press whatever I have set as the Terminal shortcut in Switchboard → Keyboard → Applications (which by the way fails to actually open my terminal). None of the shortcuts defined for the other functions triggers this issue, only the Terminal one.

[J. Antonio Romero (nsdragon)]

This bug might be what's actually going on: https://bugs.launchpad.net/elementaryos/+bug/1355150

[mako (marcus-yass-a)]

1355150 does not get to the heart of the problem. I'm getting this same issue despite never touching x-terminal-emulator. Albeit I'm not using Elementary, but clearly whatever's pumping out these messages is not directly related to x-terminal-emulator.

I add that the numbers being produced are increasing over time.

[mako (marcus-yass-a)]

I retract my comment. On reflection, repeated Hellos and NameOwnerChangeds are too generic an error to assume the cause is the same.