https://bugs.kde.org/show_bug.cgi?id=466193
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #6 from David Edmundson <k...@davidedmundson.co.uk> ---
Don't make a patch doing that.
Blocking plasma from starting until KAMD is fully up would make everything
slower and is missing some key parts of the story.
KActivityManager daemon is DBus activated. Plasmashell will make a call to kamd
track progress that way. It does it internally, that's why we don't have a
strict systemd dependency.
we can see someone doing that here:
>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…
dbus-daemon should keep track of that all things and let plasmashell know which
has it's own tracking. If we get in to the error path listed it means we've
been told that starting
If you get the error listed it means plasmashell explicitly thinks kamd failed
to start rather than a race. Can you attach the non-abridged logs.
--
You are receiving this mail because:
You are watching all bug changes.
