I agree with LiSrt. This bug is very reproducible, though unfortunately not on cue. I have reported it as well in https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/713157, though I just marked that as a duplicate of this one. If someone would let me know what to harvest, I'd be willing to help. The bug is VERY annoying, basically every couple of days I have to shut down all my open work, log out, log back in, then re-open everything I was working on. Quite a time killer. Since it's basically impossible (or at least I can't figure out how) to view bugs marked as "Fix Released" unless you already know about it, I'm changing it back to "Incomplete." It definitely isn't fixed! Would a status of "New" be more appropriate? I'm not very familiar with this process.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680444 Title: dbus-daemon eats 100% cpu and is not responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/680444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
