https://bugs.kde.org/show_bug.cgi?id=392288
--- Comment #6 from battagli...@gmail.com --- Actually, since that bug is listed as "fixed," it's probably better if I put my notes here. Here's what I've found: 1. I get the same problem with fractional scaling for Chrome, Firefox, Thunderbird, if I set Kwin's scaling to 1.9, GDK_SCALE=1.9, and GDK_DPI_SCALE to 0.526 (= 1/1.9). 2. Unsetting GDK_SCALE and GDK_DPI_SCALE fixes the problems in those cases, but leaves other GTK3 apps scaled incorrectly. As usual, fractional scaling ruins all sorts of things. But, whatever the solution is, it is *not* to put fractional scaling values in GDK_SCALE. If that environment variable is set at all, it must be an integer, as per the GTK-X11 documentation: https://developer.gnome.org/gtk3/stable/gtk-x11.html So we have the strange situation where if we leave GDK_SCALE and GDK_DPI_SCALE unset, Chrome/Firefox/Thunderbird somehow magically know how to follow KDE's setting and scale properly, but other GTK3 apps do not. If we set those environment variables in any way, then that fixes the other GTK3 apps, and ruins Chrome/Firefox/Thunderbird. You can't even really fix this by just rounding GDK_SCALE, and setting GDK_DPI_SCALE to its inverse. This would fix the other GTK3 apps, but would make things messy for Chrome/Firefox/Thunderbird, which would then have a different rounded scaling value applied than the smooth, correct fractional scaling they would give you by default. Some of the issues with GDK_SCALE appear to be upstream with the various browsers, which may be getting their DPI info from somewhere else to support fractional scaling. -- You are receiving this mail because: You are watching all bug changes.
