I've noticed that when this occurs in Kubuntu (10.10) killing the following
applications has temporarily resolved the issue:
- quassel
- rekonq
When I attach with gdb I get this stack trace:
#0 callback_unref (cb=0x7fee5a944850) at dbus-mainloop.c:160
#1 0x00007fee58fdfaa0 in _dbus_loop_iterate (loop=0x7fee5a6781e0, block=<value
optimized out>)
at dbus-mainloop.c:841
#2 0x00007fee58fdfefd in _dbus_loop_run (loop=0x7fee5a6781e0) at
dbus-mainloop.c:875
#3 0x00007fee58fc60cb in main (argc=<value optimized out>, argv=<value
optimized out>)
at main.c:526
Attaching dbus monitoring utilities proves unhelpful; they seem to block
waiting for the same thing other applications are waiting for.
Is this a duplicate of
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/680444?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737170
Title:
dbus-daemon uses 100% of a core's cpu time, makes it impossible to
start any applications
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
