Created attachment 165509 [details] screencast showing the issue SUMMARY I was in the process of recalibrating my internal battery and had the charge graph open. All of a sudden I noticed the fan spinning up sharply. It turned out it was kinfocenter, whose GUI layout was fluctuating between two states when the windows is maximised. See the attached screencast. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.3-arch1-1 (64-bit) Graphics Platform: X11
*** Bug 482296 has been marked as a duplicate of this bug. ***
Is this still reproducible in plasma 6.0? I had this issue on 5.27 but no longer reproducible on the master
*** Bug 488289 has been marked as a duplicate of this bug. ***
*** Bug 489399 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/228
Git commit 29d31768cfe77819211bd7322d2f55f7182af21d by Ismael Asensio. Committed on 10/02/2025 at 20:32. Pushed by iasensio into branch 'master'. kcms/energy: Fix page size flickering Make the graph height relative to the page width, instead of the column layout. This way it doesn't change when the scrollbar appears or disappears, fixing the flickering loop FIXED-IN: 6.3.1 M +2 -4 kcms/energy/ui/main.qml https://invent.kde.org/plasma/kinfocenter/-/commit/29d31768cfe77819211bd7322d2f55f7182af21d
Git commit 978f24c79f6b05f48983be405341f9c32023f29e by Ismael Asensio. Committed on 10/02/2025 at 20:44. Pushed by iasensio into branch 'Plasma/6.3'. kcms/energy: Fix page size flickering Make the graph height relative to the page width, instead of the column layout. This way it doesn't change when the scrollbar appears or disappears, fixing the flickering loop FIXED-IN: 6.3.1 (cherry picked from commit 29d31768cfe77819211bd7322d2f55f7182af21d) M +2 -3 kcms/energy/ui/main.qml https://invent.kde.org/plasma/kinfocenter/-/commit/978f24c79f6b05f48983be405341f9c32023f29e
*** Bug 499937 has been marked as a duplicate of this bug. ***