https://bugs.kde.org/show_bug.cgi?id=503802
--- Comment #4 from JMB9 <jmb_...@gmx.net> --- 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. -- You are receiving this mail because: You are watching all bug changes.
