*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The last few days I remarked vanishing konsole windows from virtual desks 2-8 by chance which were all put to virtual desk 1 ... the shrinking of konsole windows still happened (more slowly and in a random fashion - but it was not just gaps between adjacent windows), then suddenly the konsole (all using login shell) directories were all reset to "~" ... and thereafter no program was respawned after reboot - not even on virtual desk 1. So storing sizes/positions/state of programs and restoring that situation after reboot was completely broken in 3 steps - and the shrinking of konsole windows was more random and happen slowly - but this bug still exists. So with 6.0.5 nothing was fixed but all got a total mess without function. And the 'divide et impera' bug management was not a good idea (diciding shrinking and displacer etc.). Currently, Wayland and X11 are the same - nothing can be "stored on logout and restored on boot" - so session saving is no longer available with KDE neon after bug fixing ... and the next version 6.1 is announced as feature update ... I am shocked that bugs so easily to see were not spotted in tests but rolled out. And the worsening in several steps should imply that the entire code should be looked through to really fix this manyfold broken code. Thus Wayland broken and X11 annoying was a normal bug - now I can not work (my workflow requires a lot of windows [alone more than 72 windows for konsole alone plus lots of windows with okular etc.] on special places for 8 virtual desks which worked perfektly with KDE5) and thus it is major for me and should regarded that way by developers if KDE should be used on workstations ... STEPS TO REPRODUCE 1. updating KDE neon 6.0.5 after 07.06.2024 2. opening several windows and selecting session save on logout 3. rebooting ... :( OBSERVED RESULT The entire session is lost - nothing is restored (no Firefox, Thunderbird, konsole, okular ...). EXPECTED RESULT Session is properly restored with exact sizes/positions/states as it was when logging off SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon (User Edition - fully updated - no pakage problems noted) (available in About this System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Linux: 6.8.12-060812 (Ubuntu PPA - worked with that kernel before) Mesa: Mesa 24.0.8 (kisak-mesa PPA - worked with that release before) Plattform X11 (but also Wayland, which was totally broken with 6.0.0!) ADDITIONAL INFORMATION CPU: 12 × AMD Ryzen 5 3600 6-Core Processor (Zen 2) Memory: 15,5 GiB of RAM Graphic Card: AMD Radeon RX 5700 XT (RDNA 1 / Navi 10)
Just as additional info: I filed Bug 483615 for the same symptoms as this bug for Wayland on 14th March 2024. But as I checked it is absolutely the same on Wayland (since 6.0.0) and X11 (since 6.0.5). So aftre nearly 3 Months my bug report has status confitmed and no one seems to have looked at the problem - which is now a show stopper and introduced with bug fixes ... Please look at the problem - not limiting it - and test the possible fixes before rolling out on KDE neon (User Edition) ... this would have helped a lot. If some further info are needed, please call for it here (I am on the list for this bug) with a small decription as I am Unix expert and like to help fixing this severe probems.
Confirming that I'm seeing the same behavior with konsole not being restored. Bug 488355 seems to be reporting the same issue too.
Just got the update to Plasma 6.1 and the issue seems to be fixed.
I opened the new Bug 488744 as some konsole windows are just missing after reboot (seems to not be placed on virtual desk 1 or in taskbar) - but all the other problems of session saved introduced with the fixes are now gone with the feature update Plasma 6.1.0. I am happy that I can work now - and this bug should be marked as solved. The one thing still not working with session save is handled with the new bug report 488744. Thanks for all the code parts which got the fixes to come to this state.