SUMMARY As KDE 6.0 was a mess I created several bug reports - one of them: https://bugs.kde.org/show_bug.cgi?id=485273 was about shrinking konsole windows which I use to work in workstation mode: 8 virtual desks - all with at least 9 konsole windows (TeXing, programming, editing, Webserver ...). I used Session Save on X11 - as Wayland is currently not usable - and I just think that the problem my be that kwin was splitted so the infant Wayland kwin should use Session Safe via Wayland protocol - which is not even in final stage. As in 6.0 absolutely the same ill behaviour was seen and made me crazy - after many years of perfect behaviour of KDE 5. STEPS TO REPRODUCE 1. Create a normal workstation environment like: 8 virtual desks, on each having 9+ konsole windows all of 80x23 chars size and use session safe 2. Reboot several times - und you see: 3. that no konsole window has 80x23 but less - so your editing and professinal working is trashed totally OBSERVED RESULT Shrinking of all the konsole windows saved by 'session safe' which was one of the innumeral bugs of KDE 6.0 - and now resurrected again - just a little more than 2 months after I closed that Bug Report 485273. This is shocking! The old bug report has 6.5.0 in it - my fault - which may be 6.2.5 of start of 2025 when I no longer saw shrinking - and looked several weeks before closing it to be sure. And now it is back - and shrinking quite fast as before. I think it was said a rounding bug - but windows sizes are integers ... so there is hint of big problems in the programming ... EXPECTED RESULT Session save should restore all programs with correct window sizes, positions etc. - which is a task well working eben with CDE long before KDE existed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon (24.04 LTS/Noble based; daily updated) KDE Plasma Version: 6.3.4 (latest) KDE Frameworks Version: 6.13.0 Qt Version: 6.8.3 ADDITIONAL INFORMATION As this bug was very long lurring in the KDE 6.x.y and was reported by me, I am really tired about the development process which is one step forward, two steps back currently.
Are you using a fractional display scale factor, by chance?
I am not sure - but not set by me on purpose - where can I see if fractional display scale factor is set? I am sure to have only set: Display Monitor - Display Configuration - Global Scale: 150% (for my 31.5" 4k screen) and that I have not changed something about scaling in any way since the original bug was gone - so if fractional display scale factor is used, it must be change by an update of KDE neon components. If you could guide me how I can get this info, I will provide it. One more info - the current bug is more severe than the former one, as it is not a matter of several days - but every day I see new windows with less than 80x23 konsole size even when I had correct all those windows the former day. By the way - I am not sure if it has something to do with kwin or with konsole oder something else. It is probably the same problem as the former bug (Bug 485273) ... only more severe.
Thanks, the display scale of 150% is what I was thinking of - could you please test if the same issue occurs at a 100% display scale, to possibly narrow down the source of the issue?
As I am working with the workstation I am not able to use 100% - it is just too tiny. I would try to help - but I don't think that this problem is not easy to reproduce. Especially as this scaling factor was not changed on my workstation during the process of KDE development. So KDE must have introduced the old problem or invented something similar. Now each reboot makes the session save data worse - and even faster than the old bug did (which was described as rounding bug 485273), while such values should be stored with integer values. Each screen has a native resolution which should be used directly; for me scaling should have a direct effect on fonts, not on sizes of windows. I think session save should just do what it implies - getting all values and reproduce them perfectly - degrading values should never be possible at all! Not using entire pixels for windows borders and such must result in troubles. So the method would be just wrong, if I get the problem right. And what I can not get is that this bug was known and fixed - and reintroduced/-invented with (I guess) 6.3.4 - and as I thought it was solved I never guessed this could happen again ... so there from my perspective there is a problem in the development process. As I am not a developer - and never looked at the KDE source code - I just can guess. But one should make sure that problems solved can not be reintroduced later on. This should be spotted by automatic tests - I assume - or at least by changing the code that values for session save must be integers. And if it is a similar bug, the former reason for the old problems would be a good start for this 'new' problem ... and should be the way forward ... if not too many things had been changed. If so, it is a clear hint of a development problem - at least I would call it such when it happens with my own programming - but maybe kwin changes to separate Wayland from X11 my have just provoked that. On the other hand as a developer one will automatically use the highest available resolution - and 4k is cheap since 2014 - so such problems should be seen by lots of developers (Scaling fator of 100% does not make sense at all with 4k with <= 31" diagonal; and it is just strange that it is not set reasonably at the beginning). So I can not get the picture how such clear and extreme bugs are not seen or reproduced.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.