https://bugs.kde.org/show_bug.cgi?id=466193
Erik Quaeghebeur <bugs.kde....@e3q.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Erik Quaeghebeur <bugs.kde....@e3q.eu> ---
(In reply to Nate Graham from comment #1)
> > plasmashell[1162]: Aborting shell load: The activity manager daemon
> > (kactivitymanagerd) is not running.
> This indicates that your system is broken, so Plasma doesn't load properly.
> kactivitymanagerd needs to be running. Any idea why it might not be?
I looked a bit broader and kactivitymanagerd is running:
---
dbus-daemon[1035]: [session uid=1000 pid=1035] Activating via systemd: service
name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service'
requested by ':1.14' (uid=1000 pid…
…
systemd[1013]: Starting plasma-kactivitymanagerd.service...
…
plasmashell[1131]: Aborting shell load: The activity manager daemon
(kactivitymanagerd) is not running.
plasmashell[1131]: 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.
…
dbus-daemon[1035]: [session uid=1000 pid=1035] Successfully activated service
'org.kde.ActivityManager'
systemd[1013]: Started plasma-kactivitymanagerd.service.
plasmashell[1131]: Aborting shell load: The activity manager daemon
(kactivitymanagerd) is not running.
plasmashell[1131]: 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.
---
So the first seems to be a race condition: plasmashell expects
kactivitymanagerd to be ready while it is still loading. I guess the second
time the warning is logged may also be a race condition, but then with output
arriving in the log once it has already been resolved (this is all happening
within the same second).
So it seems that plasmashell should explicitly be told to wait for
kactivitymanagerd to be loaded, which is likely another bug.
--
You are receiving this mail because:
You are watching all bug changes.
