Curious how fractional scaling relates to usage of Gdk
: the output of
Gdk.Display.get_default().get_primary_monitor().get_scale_factor()
…is of type int, which seems not to go with fractional scaling.
Curious how fractional scaling relates to usage of Gdk
: the output of
Gdk.Display.get_default().get_primary_monitor().get_scale_factor()
…is of type int, which seems not to go with fractional scaling.
First thanks to @3v1n0 for making this possible in X11.
I’m trying to move away from MacOS for Web Development to Pop!_OS but I have a multimonitor setup with an old 27" Asus PB278Q that supports natively a WQHD (2560x1440) resolution and a newer 27’’ LG 27UD58-B that supports natively a 4K resolution of 3840x2160.
I tried using Wayland with fractional scaling but as mentioned by @plumerlis Firefox, Chrome & Pycharm look blurred in the 4K monitor when I choose anything different to 100% (too small) or 200% (too big).
Then I went back to the default setting in Pop!_OS 19.04 that’s X11 and enabled fractional scaling with the switch described in this post, that worked much better with no blurring.
To match both monitors to they have a similar scaling I need to set my primary monitor (27’’ LG 27UD58-B) to 150% that combined with a text-scaling-factor=1.25 worked really well but in the second monitor although it’s not scaled I only can see something like 2/3 of the desktop the rest is black.
I’m really clueless on how to fix this and this seems to be the only configuration that can work well, Firefox, Chrome & Pycharm are looking awesomely sharp, so I would like to keep it as it is but will the second monitor showing over the whole display extension.
This is how is looks like:
This is the output of xrandr
pop-os@pop-os:~/Documents$ xrandr -q
Screen 0: minimum 320 x 200, current 8192 x 2880, maximum 8192 x 8192
DP-1 connected primary 5120x2880+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
3840x2160 60.00*+ 60.00 50.00 59.94 30.00 30.00 30.00 25.00 25.00 24.00 24.00 29.97 23.98
2560x1440 59.95
1920x1080 60.00 60.00 59.94 30.00 24.00 29.97 23.98
1920x1080i 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.91
1152x864 59.97
1280x720 60.00 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 60.00 59.94 59.94
640x480 60.00 59.94 59.94
DP-2 connected 5120x2880+5120+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95*+
1920x1080 60.00 60.00 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 59.90
1280x960 60.00
1280x800 59.91
1152x864 75.00
1280x720 60.00 60.00 50.00 50.00 59.94
1440x576 50.00 50.00
1024x768 75.03 70.07 60.00
1440x480 60.00 60.00 59.94 59.94
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00 50.00 50.00
720x480 60.00 60.00 59.94 59.94 59.94
640x480 75.00 66.67 60.00 59.94 59.94
720x400 70.08
HDMI-1 disconnected (normal left inverted right x axis y axis)
Did you manage to fix this?
The same problem started happening to me this week on ubuntu 19.04.
I created an issue for gnome: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1897
Apparently, this is an ubuntu issue. I’ve opened one here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852864