| 2013-05-06 06:14:27 |
subramaniajeeva@gmail.com |
description |
Ubuntu version : 13.04
Architecture : x86_64
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 |
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 |
|
