*** 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 After Plasma 6.1.0 most problems of Session Safe were gone (cf. Bug 488264) - instead of one special: there are now 4 konsole windows missing after 1st reboot - and differently to problems before there are not shifted to virtual desk 1 (I have 8 virtual desks each with 9 konsole windows - I worked several years with that set under KDE 5 without any problem). Those 4 have been randomly selected - not several on one desktop but each one of the 4 on different desk and different places there - also not to find in taskbar - but just not saved with the session or deleted by some strange condition (? just guessing ?) ... STEPS TO REPRODUCE 1. Update to Plasma 6.1.0 under X11 session - 8 virtual desks each with 9 konsole windows (each with special starting directories using login shells - for completeness - should not have any result on the outcome) 2. Session saved after login - and just initiate reboot 3. Aftert reboot all konsoles are there incl. correct directory - but some are missing OBSERVED RESULT In the regular pattern of 9 konsole windows one can directly see that a few are missing. EXPECTED RESULT Each window present on logout should be present after a reboot (So similar to this old screenshot showing some additionol konsole windows: https://www.jmb-edu.de/images/Typical_Virtual_Desktop_KDE_neon_6_0_3_X11_JMB.png) SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: KDE neon 6.1.0 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION 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)
After updating to 6.1 a boot missed some windows. Next boot was complete concerning all konsole windows. So I will look at it and if after a week no problem appeared, this bug would be due to the complicated changes and no longer a problem with KDE 6.1.0 and will then gave the status resolved.
Ok, now I can definitely confirm that the bug is real. My settings of 72 konsole windows (9 on each virtual desks) will show about each 3 boots a not complete setting (about 1-3 konsole windows not respawned) - while I check the setting before shutdown. So the are not saved or respawned correctly ... Additionally on each desk the is an item collecting all konsole windows and here there is a bar to switch it from left to right - but the bar can (worked before 6.0.5 under X11) not be clicked and swiped to a side ... so some other window management features are also broken.
So the influx of patches for KDE seems to be strong after 6.1 - without any official release ... Thus the experience can vary. The last reboot caused all konsole windows to lose the last directory path ... which should be regarded as a major bug for workstations (maybe a separate bug). But of cause if the Qt changes / framwork is resonsible, bug fixes could cause temporary loss - so hard to say for any tester. Additionally, one konsole window was just missing (not respawned - which is the topic of this bug report - so definetely valid). So the next step for me will be a bug report to get konsole fully functional to be invoced by scripting (the lack of this is a cear regression ... even though also present in KDE 5). Thus a tester can clearly decide if konsole is the one to blame or something built in save session (storing data and respawning everything according to that data). And a workstation usage would still be possible by scripting all konsole windows on all virtual desks - e.g. as workaround for a broken session save feature. But this bug report is valid for current KDE neon with Plasma 6.1 and all new updates released till now, unfortunately. But it is not that clear/frequently as before - but still not fixed.
After last comment Plasma 6.1.1 was available - I updated and change the directorie to see if there were some improvements; but now no konsole window was respawn - no okular was respowned - the ony program which was respawned was Firefox installed in special directory from Mozillar tar.bz2. So now (maybe only as intermidiate state) save session is destroyed as it was around 6.0.5. I wonder why one should test KDE if developer can never have tested 6.0.0, 6.0.5 or 6.1.1 - totally broken and visible directly when really working. These should have never went on KDE neon User Edition!
The problems are changing form 6.1 to further updates to 6.1.1 - but after 3 devasting patches which ruined the entire session since 6.0, with 6.1.1 now after 2 reboots 6.1.1 it seems to get quite stable for session save: but missing konsole windows or displaced ones are seldom but clearly happening. From my point of view the code must be prone to bugs so should be checked as a whole - these random annoyances are not easy to trigger - but I am sure it just happens with the latest KDE neon patches - no updates pending as checked right now.
The ongoing development process is a real burdon. When staring this morning (28,06.2024) repawn works except that all konsole windows lost the directory path (all ~). When logging out, only Firefox respawned - a pattern well known, unfortunately - so Save Session was completely ruined for the 4th time since introduction of Plasma 6.0.0! As all desktop savings were lost I tested Wayland - no Save Session at all. So this is stable - in a broken way ... But there were new KDE updates emerging and it looks like Save Session may work again. So this bug report may get updated again when I tested this version for some time without new devastating KDE updates in the meantime ... I hope the development process it not AI based ... but this would explain a lot ...
Today the session saved was just firefox - again - so the current 6.1.1 Save Session under X11 it totally broken - and the one under Wayland was never exitisting since 6.0.0 ... so no professional wirkflow possible with KDE neon 6.1.1. Thus the error report for this bug (tested to be still existing) is no longer really testable as everything is - again ... destroyed. And the same pattern as around 6.0.4 - konsole windows lose direcectory, after a reboot no konsole or okular window etc. is respawned. I am still reflecting why Firefox is the only program still respawned ... And why the developers build in the same error patterns again and again and can not keep the status of of working desktop environment ... a pletora of bugs - ok - but one should at least test for bugs which return - this should be in the developers interest ... But I think testers / bug report are no longer taken seriously ... would really like to have PM with a developer to understand why all this happens again - and again - and again - and no one listens ... just sad.
Till KDE Plasma 6.1.3 the problem is still there ... only 6.1.0 worked for me ... --- About every 5 reboots all konsole windows lose their directories (and use ~ instead), and after the next reboot nothing will come up (except firefox). --- The original problem of missing windows or displaced ones are random and not very frequent ... but is clearly there ... so there must be several problems involved AFAIK ... --- But no real hint to get to the root of that problem ...
Adding the x11-only keyword
As Wayland is not even usable with session save, this problem is X11 only till Wayland is capable of basic KDE functions. As of Plasma 6.3.0 (maybe even 6.2.5? - KDE neon based on Jammy is unfortunately still broken - so 6.2.0 was definitely still buggy) this problem did not occur. As I am depending on session save in a huge way, I can say that the bug is no longer there. As this problem occurred sporadically, I just wanted to be sure. This bug report can be closed - so I set the status to Resolved - Fixed.