Is there some new feature in X11 KDE6.2 that tries to adjust window sizes when a connected monitor is powered up or down in a multi-monitor desktop?
I have two monitors, when I power down the right monitor, the pycharm window in the left monitor increases in size. The same thing happens with a Qt script I’ve written. My script appears to receive a Qt resize event immediately when I toggle power on the left monitor.
- Is this a bug or a feature?
- Is there a way to turn off this resizing behaviour?
It kind of looks like KDE6 might be trying to remember how windows were sized in each configuration of monitors and restore it on switching - I would definitely like an option to turn that off.
Operating System: openSUSE Tumbleweed 20241028
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2
Manufacturer: ASUS
1 Like
I have the same problem. In my case several windows (Telegram Desktop, KeePassXC) get smaller. Other programs (Firefox, Thunderbird, VS Code) are not affected, so it may affect Qt programs specifically.
One display is connected via DP (secondary), the other via HDMI (primary). This is somewhat buggy already, for example SDDM treats the DP monitor as primary and many programs open there instead of the configured primary monitor.
Operating System: NixOS 24.11
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.6.69 (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon RX 5600 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C37
System Version: 3.0
Hmm…over the past couple years, there have been a few bugs pop up on-and-off with something similar happening:
That last one is the only one that I see from a quick scan that’s on Plasma 6 - it looks like this issue has been a bit tricky to totally pin down, so it does sound quite possible that it might have popped up again.
Others here might have ideas on how to work around what you’re seeing, but barring that, I’d personally recommend reporting it as a distinct issue (since what you’re seeing might be subtly different from past reports) via the KDE Bugtracking System: Get Involved/Issue Reporting - KDE Community Wiki
1 Like