dbus-daemon consumes 100% cpu after login

Bug #1176481 reported by subramaniajeeva@gmail.com
48
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned
dbus (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Ubuntu version : 13.04
Architecture : x86_64
Problem in : gnome-classic
dbus:
  Installed: 1.6.8-1ubuntu6
  Candidate: 1.6.8-1ubuntu6
  Version table:
 *** 1.6.8-1ubuntu6 0
        500 http://in.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

Frequent problems with dbus-daemon entering a runaway state, consuming 100% of one core for extended durations. KDE applications fail to open or react in a timely manner while this is happening. Couldn't open firefox, terminal, system monitor, vlc, gedit , etc...
Previously, I've been using 32 bit ubuntu with no problems (ever). This problem is there since I installed ubuntu 13.04.

Reproducible: Yes

Steps to Reproduce: Seems linked to login duration, running KDE apps (or dbus enabled apps) include: Firefox, Network Manager.

Actual Results: One core at sustained 97(+)% cpu. dbus-daemon highest process in "top" output. Killing dbus-daemon clears CPU utilization, but then all KDE and dbus applications(like firefox, nautilus, network manager applet) fail to run until restart.

Expected Results: dbus-daemon should not runaway.

ps -ef output for dbus-daemon process:

102 974 1 0 08:34 ? 00:00:00 dbus-daemon --system --fork
jeeva 1866 1 31 08:34 ? 00:25:22 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
jeeva 1880 1876 0 08:34 ? 00:00:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3

Tags: amd64 raring
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report, why do you think dbus using cpu is a lightdm issue? One reason of the cpu usage could be that a client is "spamming" the bus, is there high activity reported on the bus by dbus-monitor when that happens?

Changed in lightdm (Ubuntu):
importance: Undecided → Low
affects: gdm (Ubuntu) → ubuntu
Revision history for this message
subramaniajeeva@gmail.com (subramaniajeeva-y) wrote :

I'm Sorry to put this bug under lightdm. I tried to put the package as dbus. It didn't workout. so, I clicked the option "I don't know the package". It automatically took it as lightdm.

Also I get some problem with login screen. Sometimes the login text box became very large. Not only that the whole screen, font, panel everything is becoming very large. I try to shut down the system. It is not shutting down. Is this bug related to lightdm?

affects: lightdm (Ubuntu) → edbus (Ubuntu)
papukaija (papukaija)
affects: edbus (Ubuntu) → dbus (Ubuntu)
Changed in ubuntu:
status: New → Invalid
tags: added: amd64
summary: - dbus-daemon consumes 100% cpu after login in ubuntu 13.04
+ dbus-daemon consumes 100% cpu after login
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.