Bug 437551

Summary: Session restore doesn't restore windows to the correct activity/desktop
Product: [Unmaintained] ksmserver Reporter: Ondrej Mosnáček <omosnacek>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs, rdieter
Priority: NOR    
Version: 5.21.5   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ondrej Mosnáček 2021-05-23 15:15:58 UTC 
SUMMARY
After upgrading from F33 to F34 (i.e. plasma-workspace 5.20.5 -> 5.21.4, I think), session restore no longer remembers the activity and virtual desktop that it was on, restoring all windows into one activity and desktop.

I have around 5-6 active activities, which I use to switch between projects I'm working on, with several windows in each of them, so this completely breaks my session after a reboot :(

Note that I still use X11 session, not Wayland.

STEPS TO REPRODUCE
1. Login, open some windows in different activities and desktops.
2. Reboot and login again.

OBSERVED RESULT
All windows open in a single activity and on a single virtual desktop.

EXPECTED RESULT
Each window opens in the activity/desktop where it was before reboot.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 34
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I also tired to reboot into a clean session (disabled session restore), open some windows and reboot and the issue persisted.
Comment 1 Ondrej Mosnáček 2021-05-23 15:18:59 UTC 
(In reply to Ondrej Mosnáček from comment #0)
> I also tired to reboot into a clean session (disabled session restore), open
> some windows and reboot and the issue persisted.

s/tired/tried/ and to clarify, I re-enabled restoring last session before rebooting.
Comment 2 Nate Graham 2021-05-26 18:08:10 UTC 
*** This bug has been marked as a duplicate of bug 351402 ***
Comment 3 Nate Graham 2022-05-25 17:29:31 UTC 
*** This bug has been marked as a duplicate of bug 442380 ***