https://bugs.kde.org/show_bug.cgi?id=442380
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/
|a22ff36edf108fc710e2056e7fa |93416bb280493d8173ab289903c
|5cc21447e53a3 |12ab77c67c4ae
--- Comment #100 from David Edmundson <k...@davidedmundson.co.uk> ---
Git commit 93416bb280493d8173ab289903c12ab77c67c4ae by David Edmundson.
Committed on 22/06/2022 at 12:42.
Pushed by davidedmundson into branch 'Plasma/5.25'.
Fix session restore + kwin interaction race
KSMServer sets which session to use on startup
`KSmServer::restoreSession(QString)`
When the session is up and ready either systemd or plasma-session invoke
`restoreSession()` that actively starts restoring clients.
At some point we need to notify kwin which session we're using so that
it can handle restorng window properties such as the virtual desktop.
This was done in the first call, but this has no guarantee that kwin has
started yet. Without kwin getting the DBus call it has no information to
match up restoration information.
The state RestoringWMSession is dropped as it does nothing useful.
(cherry picked from commit a22ff36edf108fc710e2056e7fa5cc21447e53a3)
M +11 -13 ksmserver/server.cpp
M +0 -1 ksmserver/server.h
https://invent.kde.org/plasma/plasma-workspace/commit/93416bb280493d8173ab289903c12ab77c67c4ae
--
You are receiving this mail because:
You are watching all bug changes.
