GNOME Bugzilla – Bug 788744
HDPI: GTK2 applications always upscaled on external monitors regardless of used scaling factor
Last modified: 2017-11-09 03:01:59 UTC
Created attachment 361205 [details] Screenshot of Google Chrome upscaled despite scaling factor set to 1 A have a laptop with a HDPI screen connected to a docking station with two external FullHD monitors (no HIDPI). When connected to the dock, I usally turn off the laptop's built-in display and use a scaling-factor of 1 for the external monitors. Since updating to Gnome 3.26.1 I have problems with GTK2 applications not respecting the set scaling factor. E.g. Google Chrome, Firefox or Gimp are upscaled (to twice the original size) regardless of the current scaling factor (see attached screenshot). With Gnome 3.24 (and prior versions) I was able to set the scale factor via the following command or using Gnome Tweak Tool and all applications were scaled accordingly. gsettings set org.gnome.desktop.interface scaling-factor 1 In Gnome 3.26 the window scaling setting was removed from "Tweaks" and is now part of the Gnome settings. However, the setting is only shown when the external monitors are not connected. Setting the scaling factor using the command above only affects GTK3 applications. Logging out and back in or restarting Gnome shell doesn't solve the issue. It occurs on both Wayland and X. I am not sure, if this issue is actually related with Mutter. If not, feel free to move it accordingly. My system runs Gnome 3.26.1 on Arch Linux.
Google Chrome and Firefox both use GTK3.
Okay, I wasn't aware that Firefox and Chrome already use GTK3. Maybe the issue isn't related with GTK2. But in fact there is a problem with these applications in the described scenario.
Might be the same issue as in https://bugzilla.gnome.org/show_bug.cgi?id=788040
The issue is still there in Gnome 3.26.2 although https://bugzilla.gnome.org/show_bug.cgi?id=788820 is marked as fixed. Is that patch already released? Maybe the issues aren't related contrary to my previous assumption.
I managed to solve the issue. The problem was that the gsetting org.gnome.settings-daemon.plugins.xsettings was somehow set to {'Gtk/ShellShowsAppMenu': <0>}. The solution was to revert it to the default value, which is {}. The gsetting org.gnome.desktop.interface scaling-factor doesn't seem to have any effect anymore.
(In reply to Michael Rapp from comment #5) ... > The gsetting org.gnome.desktop.interface scaling-factor doesn't seem to have > any effect anymore. It will override default monitor scale when generating a configuration, but if you have ever changed it from the control center then it wont have any effect. The proper way to change any scale now is to do so via the control center / monitor configuration, as any global scaling factor is limiting functionality on Wayland.