https://bugs.kde.org/show_bug.cgi?id=442380
--- Comment #86 from Brian Kaye <b...@unb.ca> --- (In reply to Nicolas Pomarede from comment #85) > (In reply to Kishore Gopalakrishnan from comment #70) > > Can someone confirm if disabling Plasma's systemd-based startup fixes the > > issue? To disable it, run > > kwriteconfig5 --file startkderc --group General --key systemdBoot false > > in a terminal and reboot. > > At least for me, session restore seems to work perfectly (remembers which > > virtual desktops and activities windows were on) on X11 when this is > > disabled. > Thanks for this, it fixed my restore issue on my laptop PC. After several > reboots, windows are correctly restored on their respective virtual desktop. > But I have mixed results that might match what other reported : I have 2 PC > with exact same packages (Mageia 9 dev version), 1 laptop and 1 "normal" pc. > On the laptop, session restoring is working again after disabling systemd > for kde, but on the other PC session is still not correctly restored (using > the same apps (konsole, kwrite, kate) than on the laptop). > > So, this really looks like some kind of race condition to me ; starting kde > from systemd seems to start components in the wrong order or not waiting > enough to ensure each component had enough time to start fully and handle > session restoring for example. > On my other PC it still doesn't work as if even when kde starts each > component itself (not with systemd) then some parts are not ready to handle > session restoring. > > In the end, we see that code for restoring session is still working in > recent KDE/Plasme, in the sense that session is saved and can be loaded > later on next login, but it seems to me that the process that try to restore > the session happens too soon / at the wrong time when kde/plasma is not > ready yet. I agree. See my comment 29. -- You are receiving this mail because: You are watching all bug changes.
