SUMMARY *** I open several programs incl. a lot of konsole windows (~72 about 8 virtual desktops; oldschool way of working with a workstation ;). Configuration: "Settings - Session - Desktop session - Session restore: launching ... open: on last logout" which worked perfectly with KDE5. I have not looked for more programs - but Firefox and Thunderbird is restarted after having started them now ... never worked for Konsole since KDE 6.0.0 on my system. I also changed the setting, rebooted, changed it back ... never worked under 6.0.0|2. It did work with other OS - and KDE neon with up to 5.27.10, but was no longer working with update to 6.0.0 and unfortunately no change with next update to 6.0.2. *** STEPS TO REPRODUCE 1. Configuring session save after reboot to restore session 2. Open several konsole windows ... 3. Rebooting - an no konsole window is present at all ... OBSERVED RESULT No konsole window is respawned after booting the system. EXPECTED RESULT All konsole windows present bedore boot are respawned after booting with correct size, directory and position for all virtual desktops (I use 8 in a row). SOFTWARE/OS VERSIONS KDE neon current [Ubuntu 22.04 LTS based] ADDITIONAL INFORMATION ... would not think any other thing could be of relevance ... should be reproducable on any HW ... I am a former Unix specialist - so if you need futher details or have problems to reproduce this problem, just ask with some explanation what to do / send to you for clarification. E-Mail: jmb_tux@gmx.net Thanks for your good job! End of Problem description! If the rest would be a reasonable bug report please say so and I will create it ... but may be helpful when looking at the problem - at least I hope so ... # # * Little off-topic - about finding a workaround for that problem # (currently, I can not work as I need a lot of konsole-Windows # which take a lot of time to get 72 of them in right size and position # after each boot): # # I tried creating konsole windows with fixed size and positions, but # while size of window was accepted, the position did not work - it always # emerge in the middle of screen and title can not be set: # konsole --qwindowgeometry 400x400+50+50 --workdir '/home2/jmb/mytex/presentation_jmb/' --hide-menubar --hide-tabbar --notransparency --qwindowtitle 'JMB_Term_1' & # # -> "JMB_Term_1" does not work - maybe a console setting ... will check. # -> --qwindowgeometry was found via command 'konsole --help-all' under # KDE 6.0.2 but first two parameters work (width and height of window) but # next parameters have no meaning ... always respawning in the middle. # -> There seems to be no Konsole Manual for version 6 yet # (KDE5_konsole_handbook.pdf is not helping - I think). # # Im not sure if the 8 virtual screen (6x 8k in a row) should be positions # just by incresing x position - as it worked several years before using KDE # working with XFCE, e.g.: # xfce4-terminal --geometry 80x22+1530+1509 --working-directory=/home/user/mails -T "User@`hostname` `date +%a.,\ %d.%m.%Y\ %H:%M:%S`" & # # Some explanations may be helpful for a lot of KDE users concerning # CLI usage of konsoles for scripting - I guess.
I can confirm this issue on Arch Linux. Konsole windows are no longer restarted.
Confirmed on a fully updated Neon following the original instructions. Can be duplicated every time. If I launch Firefox, Konsole, Dolphin, Discover, and Kate, then log-off, and log-in again, only Firefox is restored.
Problem appears Wayland related. Switch to X11 and all apps respawn fine after logging out and in again,
Yes, when selecting X11 session it seems to work for me - applying the same scaling, X11 is larger then Wayland ... this may be addressed, too (at least if KDE is expected to have same appearance under both session type - which I would prefer).
Hi JMB9 regarding "applying the same scaling, X11 is larger then Wayland" - would you mind raising this as a new bug (perhaps check in case someone has done so already beforehand)? Thanks.
New 3rd bug report seems not necessary: Well, the problem with size difference is caused by me selecting 155% on Wayland (after the former factor was not applied but was put to 100% when updating to KDE6 - which is really tiny), while on X11 session the global scale was set to 200% (I don't know why) - so this it was a little too large. But setting it to 155% on X11 seems to be quite similar (eben idetical) with using Wayland and 155%. So the only thing which was not perfect is that both saling factors are not adopted in the other session after changing it. But maybe there exist reasons that this would not be appropriate - so I think this is not worth a bug report - as long as switching between X11 and Wayland with same look and feel is a goal of KDE. Concerning the main problem I found that: 1) X11 session: a) is able to store the konsole windows - and when switching to 2) Wayland those correctly restored konsoles are a) opened with correct windows size (OK) but b) are respawned in the middle of 1st virtual desktop - so window position can not be restored (bug with Wayland). After my findings the position is just not considered in Wayland session. c) konsoles are never saved with session save (bug with Wayland). So both, not saving and not use windows position of konsole windows are severe bugs for people like me working with about 72 konsole windows. So here, Wayland makes trouble while X11 works as it should. On the other hand even with X11 and command line I can not position konsole windows as I wich for (despite being possible in session save): a) I am not able to give a parameter concerning virtual desktop - as it is used by session restore one should give it with parameters; b) larger positions than screen resolution is not interpreted to be sent to further virtual desks (fvwm used virtual coordinates in the 1990-ies - very easy placement for all desktops) but are shifted "last pixel + 1" to "1st pixel" of the current virtual desktop with KDE. For me, this is also a bug - but maybe just a problem of missing help text? Is there any document (web or PDF manual) explaining how to create such konsole windows correctly with KDE6? I tested something like (I did not see more when using 'konsole --help-all' on KDE6): konsole --qwindowgeometry 400x400+50+50 --workdir '/home2/jmb/mytex/' --hide-menubar --hide-tabbar --notransparency --qwindowtitle 'JMB_Term_1' but this is not working for Virtual Desktops and not for Window title - but I am new to this method of creating all windows via a simple script. This could be invoked at session start and no longer saving a session ... which would ba a more robust approach. So not only a workaround but just working more efficient and customizable.
This bug is about a special Wayland issue with KDE6 - unfortunately X11 has also a bug which changes the size of windows sizes (at least for konsole it seem every boot can change it to make them smaller - the pattern seems random at first) ... and I opened Bug 485273 for this different problem ... it could be that while quite different both problems may be related.
Just to make clear that the same problem (but clearly concerning different code passages) is now present for X11 session (see Bug 488264). As this can be regarded as different bug as Wayland session save was trashed with 6.0.0 and X11 session saved was trashed around 6.0.5 in different steps which are described in the new Bug report 488264 ... So changing size on X11 is a minor problem of the past - now KDE neon is no longer capable to restore a session at all - which makes it no longer a place to work for me using a lot of konsole and okular windows with fixed positions on 8 virtual desk ... after three months of bugfixes Wayland is still broken (checked it) and by 'fixes' it is broken for X11, too.
Unfortunalely Wayland session is still not capable of performing session save ... while X11 is now fixed with Plasma 6.1.0 in most situations (see resolved Bug 488264). On the other hand starting programs work under Wayland - no graphics' errors spotted (after the strange partly-dead pixel problem was solved) and working was possible. But session save is important for workstation use ... so currently Wayland is not ready to get ones work done. So in case Wayland should be aimed to become the session default this must be fixed first.