Created attachment 178017 [details] Reproduction screencast for `#c0`. SUMMARY ------- Resizing a Kirigami-based application (like NeoChat) from the bottom of its window causes its interface to jutter during the resize. This does not occur when resizing the same application from elsewhere, and does not occur to QtWidgets-based GUIs (like Dolphin). STEPS TO REPRODUCE ------------------ 1. Install: - `neochat-24.12.1-1.fc41.x86_64` via DNF5; or: - [`io.github.ebonjaeger.bluejay`][1] at commit `00663ccd4760811d054f4c602d7294f59d544fafe4ed6562f82990244cb7e567` via Flatpak. 2. Resize from the *bottom* of the window. 3. *To compare*, resize from the sides or top. OBSERVED RESULT --------------- - When resizing from the bottom, the interface jutters until the resize has completed. - When resizing from elsewhere, the interface responds smoothly, as one would expect from QtWidgets. EXPECTED RESULT --------------- Solely the latter, obviously. SOFTWARE/OS VERSIONS -------------------- 1. ~~~sh #!/usr/bin/env sh kinfo ~~~ 2. > ~~~YAML > Operating System: Fedora Linux 41 > KDE Plasma Version: 6.2.5 > KDE Frameworks Version: 6.10.0 > Qt Version: 6.8.1 > Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor > Memory: 30.4 GiB of RAM > Graphics Processor: AMD Radeon RX 5700 > ~~~ ADDITIONAL INFORMATION ---------------------- I've `kf6-kirigami-6.10.0-1.fc41.x86_64` installed, solely as a dependency. [1]: https://dl.flathub.org/repo/appstream/io.github.ebonjaeger.bluejay.flatpakref
Hi - I can't reproduce on my Fedora KDE 41 device. Just to double-check, does the issue reproduce on your system if you have the default fonts/sizes set?
(In reply to John Kizer from comment #1) It reproduces with the defaults, insofar as `kcm_fonts`’ "Defaults" button applies them. These are: 1. `google-noto-sans-fonts-20240701-2.fc41.noarch` 2. `google-noto-sans-mono-fonts-20240701-2.fc41.noarch`
This was a Qt issue that was fixed in Qt 6.9, which is released now.
(In reply to Nate Graham from comment #3) Could you link to the relevant bug, if you still remember which?
I can't find it, sorry