https://bugs.kde.org/show_bug.cgi?id=429443
--- Comment #1 from [email protected] --- Seems it did that because $DBUS_SESSION_BUS_ADDRESS was not set. It's set now so it's solved for me now but the high usage when unable to find the dbus is probably still not desirable. -- You are receiving this mail because: You are watching all bug changes.
