I will try to come up with a distilled down test case illustrating that libdbus-cpp is not the cause but a symptom of the issue. Point being that it certainly shows up in the stack traces, but it sits waiting in all of them (specifically for the system settings crash).
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: Apps and services use large amount of CPU after unity8 resets To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
