SUMMARY Since about Saturday, everytime I open a new project (like Okular or KWidgetsAddons), the KDevelop main window’s geometry gets destroyed right when the CMake error message appears. STEPS TO REPRODUCE 1. Damage your gettext install, so CMake will fail at every initial run. 2. Open a project in KDevelop, where CMake will be configured and run automatically. 3. CMake runs, and fails because of gettext. 4. The error message that CMake failed, and code understanding will not work, appears. OBSERVED RESULT The window resizes from “maximized” to “maximized, but much bigger than my screen”. I can “restore” and “maximize” it as usual, but all the side panels can not be resized to more than “very narrow” anymore. I have to restart KDevelop to continue work. EXPECTED RESULT Window geometry intact. SOFTWARE/OS VERSIONS KDE Neon 5.20 KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75 Qt Version: 5.15.0
how large is your screen? can you paste a screenshot - I guess the error message is too large and we need to enable text elision?
My screen is 1920x1080, with a global screen scale of 131.25%. Screenshot does not work, because I can’t reproduce it anymore. Maybe my observations were wrong, and I need to do something else.
The error message takes 4 text lines now. Possible that the window resized by the size of the error message, and the size hint of the text editor changed to the current size with size policy “minimal”, so I couldn’t make the side panels bigger than the error message.
Created attachment 132611 [details] Geometry broken again after causing a CMake failure and opening a deleted file while the error message is still shown. I think I found how to trigger this, I need to open another file while the error message is shown.
Created attachment 132612 [details] Video how opening a deleted file apparently breaks geometry Thats it. Apparently it doesn’t need a CMake failure to break geometry, opening a deleted file seems to be enough, and the error message just makes it visible.
huh, very odd. do you have time to look at this? I'd start by attaching gammaray after the issue occurred to check if it's really the size hint or something else that triggers this?