Summary: | Java applications start with wrong scaling on mixed scale monitors | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | elman |
Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | kde, nate |
Priority: | NOR | Keywords: | multiscreen, qt6 |
Version: | 6.0.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=477177 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
elman
2024-03-13 04:25:52 UTC
Are all affected apps using XWayland, or are any of the affected apps running as native Wayland apps? Does it change anything if you go to System Settings > Display and Monitor and change the value of the "Legacy Applications (X11):" setting? If it does, does it make a difference for all previously-affected apps, or only some? XWayland - RubyMine - PHPStorm - LanguageTool plugin in LibreOffice Wayland - DBeaver When I set "Scaled by the system", XWayland apps are scaled to 100% on FHD screen and to 200% on 4K, but are blurry. When I set "Apply scaling themselves", I manually configured RubyMine and PHPStorm to use 200% scaling. I did a lot of testing and this behaviour is erratic. Sometimes apps start on 4K, sometimes on FHD (I always keep cursor on 4K). Sometimes they start with correct scaling, sometimes not. And sometimes when I move windows between screens scaling gets "fixed" and sometimes it changes to 50%. Couldn't find any pattern to it… Ok, I'm pretty sure I know what's going on here: when you use the default "Apply scaling themselves" feature, KWin is relying on apps to have sane X11 digh DPI behavior. Evidently these apps don't, unfortunately. The fact that you can configure the scale in the apps on a per-app basis is a dead giveaway. Obviously this won't work in a mixed-DPI screen setup since the scale you set for an app that makes it look good on one screen won't be correct on the other screen. I have a feeling the apps are trying to be smart and fighting the system, outsmarting themselves in the process, and this is what accounts for the erratic results. |