[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Nate Graham changed: What|Removed |Added Summary|Session restore does not|With systemd boot, session |remember which windows were |restore does not remember |on which virtual desktop on |which windows were on which |X11 |virtual desktop on X11 Version|5.24.2 |5.25.0 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #93 from David Edmundson --- The DBus call to kwin to say which session to use fails. In my logs I see ksmserver make the call before: Jun 17 15:36:56 david-desktop systemd[922]: plasma-kwin_x11.service: D-Bus name org.kde.KWin now owned by :1.10 In fact we see plasma-restoresession.service super duper early - could explain som kwallet issues. It's set to be: "After=graphical-session.target" which I didn't think should count as up until p-w.target is -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Nate Graham changed: What|Removed |Added CC||cuentabas...@gmx.com --- Comment #94 from Nate Graham --- *** Bug 455471 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #95 from Natalie Clarius --- Re. me getting the bug even with systemd boot disabled: It hadn't occured to me earlier that that would make a difference, but I'm normally running source-built KWin on top of stable Plasma (with an XSession file setting the KDEWM variable), and when I just tested logging into the normal session a few times, everything seemed to be restored correctly. So I'm taking back what I said earlier, and it probably really is solely a matter of how things are started up. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Michael Hamilton changed: What|Removed |Added CC||mich...@actrix.gen.nz --- Comment #96 from Michael Hamilton --- I just upgraded to openSUSE Tumbleweed 20220616 with KDE Plasma 5.25 and on login immediately experienced this bug. I can confirm the expected/correct login session behaviour was restored after disabling systemdBoot by having the session user perform: kwriteconfig5 --file startkderc --group General --key systemdBoot false -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Paul Worrall changed: What|Removed |Added CC||linus.kardell+kdebugs@gmail ||.com --- Comment #97 from Paul Worrall --- *** Bug 455591 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #98 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1859 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||a22ff36edf108fc710e2056e7fa ||5cc21447e53a3 --- Comment #99 from David Edmundson --- Git commit a22ff36edf108fc710e2056e7fa5cc21447e53a3 by David Edmundson. Committed on 22/06/2022 at 11:30. Pushed by davidedmundson into branch 'master'. 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. M +11 -13 ksmserver/server.cpp M +0-1ksmserver/server.h https://invent.kde.org/plasma/plasma-workspace/commit/a22ff36edf108fc710e2056e7fa5cc21447e53a3 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 David Edmundson 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 --- 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-1ksmserver/server.h https://invent.kde.org/plasma/plasma-workspace/commit/93416bb280493d8173ab289903c12ab77c67c4ae -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Nate Graham changed: What|Removed |Added Version Fixed In||5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #101 from Brian Kaye --- Need to get the various distros to pick this up and then turn systemd boot back on. Is the retention of files in .config/session fixed as well or is it a separate bug. Still would like to know the what the contents of the .config/session and .config/ksmserverrc files mean. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #102 from David Edmundson --- >Need to get the various distros to pick this up and then turn systemd boot >back on. Who's turned it off? >Is the retention of files in .config/session fixed as well or is it a separate >bug Unrelated to this. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #103 from Brian Kaye --- (In reply to David Edmundson from comment #102) > >Need to get the various distros to pick this up and then turn systemd boot > >back on. > > Who's turned it off? > > >Is the retention of files in .config/session fixed as well or is it a > >separate bug > > Unrelated to this. I have turned it off as a result of a comment on this bug report.. I wonder if the race condition has created the situation where the files are not deleted in .config/session. Once the distros pick up the change we will see if the deletion is still necessary. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #104 from Brian Kaye --- I ran the command "kwriteconfig5 --file startkderc --group General --key systemdBoot false" which seemed to correct the problem. The file .config/startkderc was changed(or created) . The file "/etc/xdg/startkderc" still shows "systemdBoot=true". Once the distros pick this change up (fedora has not as of this post) we will have to delete .config/startkderc or run the command "kwriteconfig5 --file startkderc --group General --key systemdBoot true" . This should be done before the fixed package is installed to verify that the new package fixes the problem. Sure wish fedora would hurry up so we can put this issue to bed. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #105 from Brian Kaye --- Ran kwriteconfig5 --file startkderc --group General --key systemdBoot true and installed "plasma-workspace-common-5.25.2-1.fc36.x86_64" and associated packages on my Fedora 36 system. Had to try a number of times before it worked though. Seems to work correctly now. But still does not remove the old files in .config/session. Probably a different bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=421870| -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 m.k...@irregular.at changed: What|Removed |Added CC||m.k...@irregular.at -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #106 from Brian Kaye --- Hopefully my last comment. Deleted all files in .config/session and started apps one at a time. All old files controlled by ksmserverrc were deleted at each logout/login. So no bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 r...@alum.mit.edu changed: What|Removed |Added CC||r...@alum.mit.edu --- Comment #107 from r...@alum.mit.edu --- Observed with openSUSE 15.3 Plasma 5.25.0 RPMs. This did not occur with Plasma 5.24; windows were restored correctly. I am running X11. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #108 from Nate Graham --- > Observed with openSUSE 15.3 Plasma 5.25.0 RPMs As the "Version Fixed In" field says, it's fixed in 5.25.2. You don't have that yet. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #109 from Natalie Clarius --- With the newest version, systemd startup enabled and accordingly the custom WM startup method switched to a systemd user unit, the problem is now resolved for my setup (source-built KWin on top of stable Plasma) as well. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #110 from Michael Hamilton --- OpenSUSE tumbleweed is now on 5.25.2. I removed ~/.config/startkderc which did contain [General] systemdBoot=false. I checked the value of kreadconfig5 --group General --key systemdBoot - it reports nothing - I presume that means the system is using the default. After logging out and logging in again, all desktops were correctly restored and ~/.config/startkderc was still absent. So the fix appears to be working for me. Is there a journal message that confirms systemd boot is now responsible for performing the restore? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #111 from Kishore Gopalakrishnan --- (In reply to Michael Hamilton from comment #110) > Is there a journal message that confirms systemd boot is now responsible for > performing the restore? After logging in, run ``` systemctl --user status plasma-restoresession.service ``` in a terminal. You should see something like ``` ○ plasma-restoresession.service - KDE Session Management Server Loaded: loaded (/usr/lib/systemd/user/plasma-restoresession.service; static) Active: inactive (dead) since Sat 2022-07-16 18:58:16 IST; 4s ago Process: 544 ExecStart=/usr/bin/qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.restoreSession (code=exited, status=0/SUCCESS) Main PID: 544 (code=exited, status=0/SUCCESS) CPU: 11ms Jul 16 18:58:14 kishorearchtestingVM systemd[392]: Starting KDE Session Management Server... Jul 16 18:58:16 kishorearchtestingVM systemd[392]: Finished KDE Session Management Server. ``` if systemd is being used for KDE's session restoration. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #112 from Michael Hamilton --- (In reply to Kishore Gopalakrishnan from comment #111) > (In reply to Michael Hamilton from comment #110) > > Is there a journal message that confirms systemd boot is now responsible for > > performing the restore? > After logging in, run > ``` > systemctl --user status plasma-restoresession.service > ``` > in a terminal. > ... Thanks. That worked and confirmed that the service had run successfully. -- You are receiving this mail because: You are watching all bug changes.
