Post History
Turns out this is a known bug in QT 5 that has been fixed in QT 6. It only happens in the following constellation, which I hit exactly: Wayland Two or more screens different scaling per scree...
Answer
#2: Post edited
by
GeraldS
·
2024-11-20T06:52:10Z (about 2 months ago)
switched the link to the release notes to the codename, which shouldn't change in the future.
- Turns out this is a [known bug in QT 5](https://bugs.kde.org/show_bug.cgi?id=432264) that has been fixed in QT 6.
- It only happens in the following constellation, which I hit exactly:
- - Wayland
- - Two or more screens
- - different scaling per screen
Sadly, Debian 13 will supposedly [still ship with KDE Plasma 5.27](https://www.debian.org/releases/testing/release-notes/whats-new.en.html#desktops-and-well-known-packages), and there are [no plans to backport the fix to QT 5](https://bugs.kde.org/show_bug.cgi?id=432264#c65), so I guess I'm going to be stuck with this bug for at least the next three years.
- Turns out this is a [known bug in QT 5](https://bugs.kde.org/show_bug.cgi?id=432264) that has been fixed in QT 6.
- It only happens in the following constellation, which I hit exactly:
- - Wayland
- - Two or more screens
- - different scaling per screen
- Sadly, Debian 13 will supposedly [still ship with KDE Plasma 5.27](https://www.debian.org/releases/trixie/release-notes/whats-new.en.html#desktops-and-well-known-packages), and there are [no plans to backport the fix to QT 5](https://bugs.kde.org/show_bug.cgi?id=432264#c65), so I guess I'm going to be stuck with this bug for at least the next three years.
#1: Initial revision
by
GeraldS
·
2024-11-20T06:49:17Z (about 2 months ago)
Turns out this is a [known bug in QT 5](https://bugs.kde.org/show_bug.cgi?id=432264) that has been fixed in QT 6. It only happens in the following constellation, which I hit exactly: - Wayland - Two or more screens - different scaling per screen Sadly, Debian 13 will supposedly [still ship with KDE Plasma 5.27](https://www.debian.org/releases/testing/release-notes/whats-new.en.html#desktops-and-well-known-packages), and there are [no plans to backport the fix to QT 5](https://bugs.kde.org/show_bug.cgi?id=432264#c65), so I guess I'm going to be stuck with this bug for at least the next three years.