https://bugs.kde.org/show_bug.cgi?id=436318
--- Comment #286 from Patrick O'Callaghan <[email protected]> --- (In reply to Patrick O'Callaghan from comment #284) > (In reply to Patrick O'Callaghan from comment #281) > > (In reply to Patrick O'Callaghan from comment #279) > > > Possible regression in Plasma 6.8: > > > > > > Since updating from Plasma 6.7.5 to Plasma 6.8.2 (Fedora 44, Wayland), on > > > session restore, windows are correctly sized and placed on desktops but > > > wrongly positioned. I have two displays, and everything appears on the > > > wrong > > > one and has to be dragged across to the original one, which is marked as > > > the > > > Default in Settings. > > > > Enabled "(In reply to Patrick O'Callaghan from comment #279) > > > Possible regression in Plasma 6.8: > > > > > > Since updating from Plasma 6.7.5 to Plasma 6.8.2 (Fedora 44, Wayland), on > > > session restore, windows are correctly sized and placed on desktops but > > > wrongly positioned. I have two displays, and everything appears on the > > > wrong > > > one and has to be dragged across to the original one, which is marked as > > > the > > > Default in Settings. > > > > Enabled "Switch desktops independently for each screen", and the issue has > > gone away. (I actually thought I already had this, but it seems not). > > > > However that doesn't really fix the problem if that option isn't enabled. If > > both screens are being treated as one large space, the window placement > > should still be preserved as the user sets it up and not arbitrarily change > > when the session is restored. > > I spoke too soon. For unrelated reasons I've rebooted my system several > times today and now most windows are not being restored. Then I kill Firefox > and restart, and some come back but not all. My Dolphin window is also gone. It turns out that the "unrelated reasons" were causing the problem. I was auto-starting a user-level daemon via systemd and it was crashing (the daemon) and session startup was being interrupted. I've fixed the problem and it seems to be working again. All the same, a failure like this shouldn't stop the rest of session restore from working, so it's really still a bug. -- You are receiving this mail because: You are watching all bug changes.
