What's the timeline for getting an update from upstream KDE on this rolled into an Kubuntu bugfix? Is there any way for me to help accelerate things? I know nothing about the way these updates get built, but this problem is affecting LOTS of people (including me) and it would be nice to get some motion from a developer on this. It's really frustrating to know that there's a fix out there (since June!), but to have no indication that anyone is working on this at Kubuntu.
How do I go about pulling the known fix from KDE, testing it with Kubuntu, and building a distribution-specific patch? Shouldn't this be pretty easy? For reference, a partial list of related bugs not yet mentioned here: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/680444 (marked as fix released, but it's not) https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/737170 (duplicate of the 680444) https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/713157 (my version of the same bug) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdelibs in Ubuntu. https://bugs.launchpad.net/bugs/779849 Title: dbus-daemon consumes 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/779849/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
