https://bugs.kde.org/show_bug.cgi?id=357170
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/3e295c33d0ee9f06c0f723a93 |t/5503d08bb1d60621304e0c60c |2f094c202af0302 |2cf0f1e6da1ccc7 --- Comment #11 from Nate Graham <[email protected]> --- Git commit 5503d08bb1d60621304e0c60c2cf0f1e6da1ccc7 by Nate Graham. Committed on 11/10/2024 at 20:08. Pushed by ngraham into branch 'Plasma/6.2'. startkde: Avoid waiting when notifying ksplash is up During startup we send signals to ksplash to let it knows components are up. To avoid a previous race ksplash uses the "waitforname" trick so any calls to notify ksplash before ksplash is up wait around before being dispatched. This unfortunately means if ksplash is disabled or explicitly closed we still hit this path and any call to ksplash will be kept alive until timeout. This systemd service is just used to notify ksplash, we don't need to wait for a response for the service to be considered done. This can block the login process, which has the side effect of inhibiting logout too. Related: bug 492492 (cherry picked from commit 3e295c33d0ee9f06c0f723a932f094c202af0302) 0198fd41 startkde: Avoid waiting when notifying ksplash is up Co-authored-by: David Edmundson <[email protected]> M +1 -1 startkde/systemd/plasma-ksplash-ready.service.in https://invent.kde.org/plasma/plasma-workspace/-/commit/5503d08bb1d60621304e0c60c2cf0f1e6da1ccc7 -- You are receiving this mail because: You are watching all bug changes.
