https://bugs.kde.org/show_bug.cgi?id=432364
hchain <henri.ch...@enioka.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://invent.kde.org/plas
| |ma/plasma-workspace/commit/
| |e7e49916712d2d8efc65d7da172
| |1eb1d31dc65d6
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from hchain <henri.ch...@enioka.com> ---
Git commit e7e49916712d2d8efc65d7da1721eb1d31dc65d6 by Henri Chain, on behalf
of David Edmundson.
Committed on 17/02/2021 at 09:53.
Pushed by davidedmundson into branch 'master'.
Move ksmserver's ksplash notifying to ksmserver
Previously the call to ksplash was being emitted by plasma-session. This
isn't used in the systemd startup so it was introduced in a somewhat
messy script.
This script has an issue:
If ksplash is disabled the bus name won't be registered. Typically this
isn't an issue. However to avoid a race condition ksplash registers
itself as being DBus activatable, so that the dbus server holds
dispatching the message.
This combo means ksmserver our unit is considered as not running until
our script times out. This then defers other things in the chain that
depend on ksmserver.
Moving the call into the relevant piece of code into ksmserver unifies
things into a single path and gives us more control.
M +0 -2 ksmserver/plasma-ksmserver.service.in
M +7 -0 ksmserver/server.cpp
M +0 -1 startkde/plasma-session/startup.cpp
https://invent.kde.org/plasma/plasma-workspace/commit/e7e49916712d2d8efc65d7da1721eb1d31dc65d6
--
You are receiving this mail because:
You are watching all bug changes.
