https://bugs.kde.org/show_bug.cgi?id=487912
--- Comment #45 from Ondrej Mosnáček <omosna...@gmail.com> --- (In reply to zb4ng from comment #44) > Whenever the bug happens, then this is in the log: > plasmashell[2581]: Qt: Session management error: Authentication Rejected, > reason : MIT-MAGIC-COOKIE-1 authentication rejected > plasmashell[2581]: Aborting shell load: The activity manager daemon > (kactivitymanagerd) is not running. > plasmashell[2581]: If this Plasma has been installed into a custom prefix, > verify that its D-Bus services dir is known to the system for the daemon to > be activatable. > see also here: https://bugs.kde.org/show_bug.cgi?id=491130#c1 > > Now the "magic cookie" is managed by the X-Server for authentication > purposes (I don't really know what's going on there and I couldn't find very > detailed info about this). > What I presume now is that there are at least two possible things that could > be the cause: > Either: Sometimes, "activity manager daemon" doesn't start in time for the > Xauthority/magic cookie stuff. > Or: The activity manager daemon doesn't start because the authentication got > rejected. Maybe plasma-plasmashell.service just needs to depend on plasma-kactivitymanagerd.service? I just tried to add the following via `systemctl --user edit plasma-plasmashell.service`: [Unit] After=plasma-kactivitymanagerd.service Will see if it helps during the next reboot(s). -- You are receiving this mail because: You are watching all bug changes.
