[nvidia] Screen scaling 125% gives 200%
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
mutter (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
Procedure used:
1.
Fully updated system via apt update && apt upgrade
2.
Select the screen setup in gnome control center
3.
Click the "Fractional scaling" toggle
4.
Select 125% and click the green "use" button top right (it says "Anvend" in dansih)
5.
Observe that the window has grown a lot, click the "use new settings" button
6.
The window tells me, I am at 200% scaling. The "200%" option is now highlighted.
7.
Switch back to 100% and file this bug.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 09:42:34 2020
InstallationDate: Installed on 2018-01-14 (810 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=da_DK.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #1 |
- CurrentDmesg.txt.txt Edit (69.9 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
- ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
- VarLogDistupgradeAptclonesystemstate.tar.gz Edit (808.9 KiB, application/x-gzip)
- VarLogDistupgradeAptlog.txt Edit (63.3 KiB, text/plain; charset="utf-8")
- VarLogDistupgradeLspcitxt.txt Edit (2.0 KiB, text/plain; charset="utf-8")
- VarLogDistupgradeMainlog.txt Edit (68.8 KiB, text/plain; charset="utf-8")
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #2 |
affects: | ubuntu-release-upgrader (Ubuntu) → gnome-control-center (Ubuntu) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #3 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #4 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #5 |
When reporting the bug, I used the nvidia-driver-435 which is not tested.
I have installed the nvidia-driver-440 and rerun the test case.
Same result: selecting 125% scaling gives 200% scaling
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #6 |
tags: | added: rls-ff-incoming |
tags: | added: regression-update |
tags: | removed: regression-update |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Sebastien Bacher (seb128) wrote : Re: Screen scaling 125% gives 200% (nvidia) | #7 |
Thank you for your bug report, could you add your 'journalctl -b 0' log after getting the issue?
summary: |
- Screen scaling 125% gives 200% + Screen scaling 125% gives 200% (nvidia) |
affects: | gnome-control-center (Ubuntu) → gnome-shell (Ubuntu) |
tags: | added: xrandr-scaling |
tags: | added: nvidia |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #8 |
The bug might still be gnome-control-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #9 |
- journalctl-b-0-logfile-scale-to-200-percent-and-back-100-percent Edit (16.0 KiB, text/plain)
Here is the journalcl -b 0 output, when scaling from 100% to 200% and back to 100%
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #10 |
- journalctl-b-0-logfile-scale-125percent-get-200-percent.log Edit (41.3 KiB, text/plain)
Oops.
The first journalctl is not the for testcast.
This is the log when I select 125 % scaling and get 200%
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #11 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in gnome-control-center (Ubuntu): | |
status: | New → Confirmed |
Changed in gnome-shell (Ubuntu): | |
status: | New → Confirmed |
Changed in mutter (Ubuntu): | |
status: | New → Confirmed |
tags: |
added: rls-ff-notfixing removed: rls-ff-incoming |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #14 |
Mh, logging isn't too useful just give us the output of the logs, please run this before doing changes from the control center
journalctl -b0 -ef /usr/bin/
Then do the change from control center and give us what the has been logged.
Also, the output for (before and after, if anything changed)
xrandr --verbose
Could you also check if the command:
xrandr --output DVI-D-0 --scale 2x2
xrandr --output DVI-D-0 --scale 1.5x1.5
Does something for you?
Cheers
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pål Andreassen (paal-andreassen) wrote : | #15 |
I have the same bug. Here are my obervartions:
xrandr --output HDMI-0 --scale 1.5x1.5 makes everything smaller (higher DPI)
xrandr --output HDMI-0 --scale 2x2 makes everything even smaller
xrandr --output HDMI-0 --scale 1x1 makes everything huge (200% according to settings)
Seems the DPI scaling has been inverted?
I tried
xrandr --output HDMI-0 --scale 0.75x0.75 and for a small instance it seems to work, and the text is at what I judge at 125%, but then a second after it switches to the overly huge 200% again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #16 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #17 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #18 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #19 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #20 |
I tried your xrandr commands:
xrandr --output DVI-D-0 --scale 2x2 ==> very small windows
xrandr --output DVI-D-0 --scale 1.5x1.5 ==> not so small windows
xrandr --output DVI-D-0 --scale 1.0x1.0 ==> back to normal
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #21 |
I followed Pål's experiments:
pj@Monster:~$ xrandr --output DVI-D-0 --scale 0.75x0.75 ==> large window & fonts, only seeing upper left part of the desktop on the screen
pj@Monster:~$ xrandr --output DVI-D-0 --scale 0.5x0.5 ==> even larger and less desktop visible
pj@Monster:~$ xrandr --output DVI-D-0 --scale 1x1 ==> NOT going back to normal
pj@Monster:~$ xrandr --output DVI-D-0 --scale 1x1 ==> Still not
pj@Monster:~$ xrandr --output DVI-D-0 --scale 1.0x1.0 ==> Stille not
pj@Monster:~$ xrandr --output DVI-D-0 --scale 2.0x2.0 ==> back to normal
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Sebastien Bacher (seb128) wrote : | #22 |
Could you also try outside of GNOME using xubuntu or another desktop to rule out shell interfering?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PerJensen (per-net-es) wrote : | #23 |
I have installed xubuntu-desktop, fully updated the system and rebooted
Xubuntu environment
===================
xrandr --output DVI-D-0 --scale 2x2 ==> very smail windows ans fonts
xrandr --output DVI-D-0 --scale 1.5x1.5 ==> not so small windows, also the fonts are a little bigger in terminal
xrandr --output DVI-D-0 --scale 1.0x1.0 ==> back to normal
Now scaling the other way:
xrandr --output DVI-D-0 --scale 0.75x0.75 ==> I see approx 1/4 of the desktop (the left upper quadrant)
xrandr --output DVI-D-0 --scale 0.5x0.5 ==> very large windows and fonts in vscode, it seems the fonts in the terminal dont scale as much
xrandr --output DVI-D-0 --scale 1.0x1.0 ==> came back to normal in 1. try
summary: |
- Screen scaling 125% gives 200% (nvidia) + [nvidia] Screen scaling 125% gives 200% |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #24 |
See also bug 1873403.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ThOR27 (thor27-gmail) wrote : | #25 |
I have exactly same problem, I've tried both 440, and 435 Nvidia drivers.
the results of:
$ xrandr --verbose --output HDMI-0 --scale 2x2
screen 0: 6880x2880 1820x762 mm 96.00dpi
crtc 0: 3440x1440 59.97 +0+0 "HDMI-0"
xrandr: Configure crtc 0 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
crtc 3: disable
crtc 4: disable
crtc 5: disable
crtc 6: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Value in failed request: 0x0
Serial number of failed request: 72
Current serial number in output stream: 72
$ xrandr --verbose --output HDMI-0 --scale 1.25x1.25
screen 0: 4300x1800 1137x476 mm 96.00dpi
crtc 0: 3440x1440 59.97 +0+0 "HDMI-0"
xrandr: Configure crtc 0 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
crtc 3: disable
crtc 4: disable
crtc 5: disable
crtc 6: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Value in failed request: 0x0
Serial number of failed request: 72
Current serial number in output stream: 72
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #26 |
I wonder if the nvidia driver doesn't support the same version/featureset of Xrandr as the modeset driver?...
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pål Andreassen (paal-andreassen) wrote : | #27 |
$ xrandr --version
xrandr program version 1.5.0
Server reports RandR version 1.6
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #28 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in nvidia-graphics-drivers (Ubuntu): | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesus (salseandotv) wrote : | #29 |
I also have the same problem, regards.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitaly Sulimov (vsulimov) wrote : | #30 |
Same for me.
Ubuntu 20.04 nvidia-driver-440, GeForce MX250.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Greg Cavazos (drayak335) wrote : | #31 |
Same for me.
Ubuntu 20.04 nvidia-driver-390 (also tried 340.108), GeForce GT-750M
I noticed some weird behavior with the xrandr, note the "mm" size is different for the same scale setting at different times.
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 2x2
screen 0: 6400x3600 846x475 mm 192.10dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25
crtc 0: disable
screen 0: 4000x2250 527x296 mm 192.51dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.5x1.5
screen 0: 4800x2700 1587x892 mm 76.81dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25
crtc 0: disable
screen 0: 4000x2250 1321x743 mm 76.88dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.5x1.5
screen 0: 4800x2700 1587x892 mm 76.81dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75
screen 0: 5600x3150 1850x1040 mm 76.88dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 2x2
screen 0: 6400x3600 2113x1188 mm 76.93dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1
crtc 0: disable
screen 0: 3200x1800 1056x594 mm 76.97dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75
screen 0: 5600x3150 1480x832 mm 96.05dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75
screen 0: 5600x3150 1480x832 mm 96.05dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1
crtc 0: disable
screen 0: 3200x1800 845x475 mm 96.17dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.25x1.25
screen 0: 4000x2250 528x297 mm 192.10dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1x1
crtc 0: disable
screen 0: 3200x1800 422x237 mm 192.42dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
greg@LapXPS:~$ xrandr --verbose --output eDP-1-1 --scale 1.75x1.75
screen 0: 5600x3150 740x416 mm 192.10dpi
crtc 0: 3200x1800 59.98 +0+0 "eDP-1-1"
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : | #32 |
I have exactly the same bug.
Ubuntu 20.04, GeForce GT 730M, using nvidia-driver-440
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ilovebytes (ilovebytes) wrote : | #33 |
i have the same problem - using a 1080ti and nvidia 440 driver - i wonder are the other versions like budgie,mate and so on also affected with this problem ?
and is someone from ubuntu/nvidia working on a possible solution- because its now nearly a full month when the bug first was reported and its still there :(
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
kitezila (kitezila) wrote : | #34 |
Ubuntu 20.04 GTX Nvidia driver 440.
After playing with xrandr --output HDMI-0 --scale YYxYY I have reached ~1.25 scale.
Steps:
1) xrandr --output HDMI-0 --scale 1.75x1.75
-- visually have increased resolution
2) xrandr --output HDMI-0 --scale 0.75x0.75
-- cause huge zoom x4-x8
3) Then xrandr --output HDMI-0 --scale 1.75x1.75
-- set resolution to expected scale of 1.25
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #35 |
This effects me also:
GeForce GTX 1060
440 tested driver
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Konstantin (soulkeeper) wrote : | #36 |
I have the same bug with fractional scaling for my Geforce 1660 Ti and 2K monitor.
The temporary solution from kitezila has worked for me too.
~$ xrandr --verbose
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
DP-2 connected primary 2560x1440+0+0 (0x1c1) normal (normal left inverted right x axis y axis) 597mm x 336mm
Identifier: 0x1bf
Timestamp: 178502
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC: 0
CRTCs: 0 1 2 3
Transform: 1.000000 0.000000 0.000000
filter:
_MUTTER_
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00fffffffffff
301d0104b53c2
0d50542108009
d1cae10081805
3500555021000
3231393438303
4678781e010a2
00504c3237393
020318f14b100
2309070783010
0820280855502
0000000000000
0000000000000
0000000000000
0000000000000
0000000000000
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: DisplayPort
supported: DisplayPort
ConnectorType: DisplayPort
ConnectorNumber: 2
_ConnectorLoca
non-desktop: 0
supported: 0, 1
2560x1440 (0x1c0) 241.500MHz +HSync -VSync +preferred
h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 88.79KHz
v: height 1440 start 1443 end 1448 total 1481 clock 59.95Hz
2560x1440 (0x1c1) 274.680MHz +HSync -VSync *current
h: width 2560 start 2568 end 2600 total 2640 skew 0 clock 104.05KHz
v: height 1440 start 1474 end 1482 total 1488 clock 69.92Hz
2048x1280 (0x1c2) 220.250MHz -HSync +VSync
h: width 2048 start 2192 end 2408 total 2768 skew 0 clock 79.57KHz
v: height 1280 start 1283 end 1289 total 1327 clock 59.96Hz
1920x1080 (0x1c3) 204.250MHz -HSync +VSync
h: width 1920 start 2056 end 2256 total 2592 skew 0 clock 78.80KHz
v: height 1080 start 1083 end 1088 total 1127 clock 69.92Hz
1920x1080 (0x1c4) 148.500MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz
1920x1080 (0x1c5) 148.350MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz
v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz
1920x1080 (0x1c6) 148.500MHz +HSync +VSync
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz
1680x1050 (0x1c7) 146.250MHz -HSync +VSync
h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.29KHz
v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz
1600x1200 (0x1c8) 162.000M...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #37 |
This effects me also:
ubuntu 20.04
GeForce GTX 1050 Ti
440 tested driver
4k monitor - displayport
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
smallcham (smallcham) wrote : | #38 |
This effects me also:
ubuntu 20.04
GeForce GTX 1660
4k monitor - displayport
I tryed '440 tested'
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
eTushar89 (etushar89) wrote : | #39 |
Affecting me too.
Ubuntu: 20.04 LTS
GPU: GeForce RTX 2070
~ uname -r
5.4.0-26-generic
~ xrandr
Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
3840x2160 60.00*+ 30.00
2560x1440 59.95
1920x1080 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1280x720 60.00 59.94
1152x864 59.96
1024x768 60.00
800x600 60.32
720x480 59.94
640x480 59.94 59.93
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
USB-C-0 disconnected (normal left inverted right x axis y axis)
~ nvidia-smi
Tue Apr 28 16:00:35 2020
+------
| NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 |
|------
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|======
| 0 GeForce RTX 2070 Off | 00000000:26:00.0 On | N/A |
| 0% 46C P8 17W / 185W | 2798MiB / 7979MiB | 3% Default |
+------
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #40 |
I am not familiar with code, so I just test what I could see... hope it helps (I posted also on bug 1873403, if not necessary I'll remove it. No intention to spam).
------------not live: tests as I remember:
without nvidia
100-->ok
125,150 too slow
with nvidia
100--> too small
200-->too big
enable fractional scaling
125-->200
150-->200
175 -->black
(stop/start freesync from monitor, restored - maybe random behavior)
2nd try
100-->ok
125-->black
(couldn't restore it, ctrl+alt+f1 & login = black again)
unistall nvidia tested drivers, try nouveau
after two changes, I could see ubuntu desktop became small or big inside my screen and around it I cound draw with the window I was holding with the mouse. If I put it inside ubuntu desktop area of my screen it works fine, outside (right column and down line) it just performs like windows xp windows when it stuck (never saw it again on ubuntu since 11.10 that I am using it).
------------live: test and keep these notes:
install nvidia again
reboot - 3rd try
100--> bigger desktop than my screen, needs to scroll (down or right) to see the rest
200--> the same
enable fractional scaling (returns to 100 by itself)
150-->black
(stop/start freesync from monitor, restored - maybe random behavior)
100 --> enable fractional-->200 by itself
I repeat it, doesn't happen the second time
150-->black
remove nvidia* through synaptic
reboot
100-->ok
125,150,175 too slow
200-->ok
install nvidia tested
100-->οκ
200-->οκ
enable fractional scale-->turn to 100 itself
150-->black
125-->200
125(200) change back to 100 first
175-->black
200-->ok
on 200, close fractional scale-->instead of return to 100 itself it doubles the area of the desktop (bigger than my real monitor area, so I have to scroll to see the rest of the desktop)
100-->100 with the same large desktop area issue
deactivate fractional scale-->issue remain
logout,logon--> 100 & ok
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Simon Ryu (neocoin) wrote : | #41 |
This effects me also:
ubuntu 20.04
GeForce GTX 1050 Ti Mobile
4k monitor - usb-c port
That work find in ubuntu 19.10 and same driver.
Changed in gnome-control-center (Ubuntu): | |
assignee: | nobody → smallcham (smallcham) |
assignee: | smallcham (smallcham) → nobody |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #42 |
Thank you everyone for your interest. Note that we do not have any use for your system specs, so you don't need to keep pasting those. This is just a software bug.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : | #43 |
I want to know how much longer this bug is fixed :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
vaughn (vaughnd) wrote : | #44 |
I have a Dell u3219q 32" and Dell p4317q with this issue. I'm trying to set 150% on the 32" and 125% on the 43", but it just goes to 200% and or goes blank. And things reset after every reboot, i.e. scaling goes wrong, monitor positioning changes, etc.
My workaround is to set fractional scaling on and 200% on both monitors, then go to the nvidia settings -> xserver display configuration -> advanced... and set the following:
32"
ViewPortIn 5120x2880
ViewPortOut 3840x2160+0+0
Panning: 5120x2880
43"
ViewPortIn 5760x3240
ViewPortOut 3800x2137+20+11 (or just 3840x2160+0+0 if you don't need underscan)
Panning: 5760x3240
This gets the scaling as near as possible, but it resets after every reboot even if you save it in the /etc/X11/xorg.conf.
Changed in gnome-shell (Ubuntu): | |
status: | Confirmed → Fix Released |
no longer affects: | gnome-shell (Ubuntu) |
Changed in mutter (Ubuntu): | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
status: | Confirmed → In Progress |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ilovebytes (ilovebytes) wrote : | #45 |
i am still affected with the bug in ubuntu - how can i get the fix ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #46 |
Still affected too (just make the latest updrades). State now:
125% --> 200% + large desktop area (I have to scroll down to find apps button and scroll right to find power)
150% -->black
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Richins (mr-grigri) wrote : | #47 |
I tried the update this morning as well and got the same effect as @Fusion.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jeffery Hancock (xkodyhuskyx) wrote : | #48 |
The scaling issue is affecting me as well:
Ubuntu 20.04 LTS
AORUS GeForce RTX™ 2080 Ti XTREME
2X Acer Predator XB281HK 4K Monitor - Displayport Connected
nvidia-driver-440
Installed alongside Windows 10
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tyler Rubin (tylerrubin) wrote : | #49 |
Scaling issue is effecting me as well:
Ubuntu 20.04 LTS
GeForce RTX 2080 Ti
Dell S2817Q
Samsung U28E590
nvidia-driver-440
Also installed alongside Windows 10
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Piotato (bareya) wrote : | #50 |
Affected as well:
Ubuntu 20.04 LTS
GeForce 1080
nvidia-driver-440
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #51 |
more test on 20.04:
100%-->125% auto200% and larger desktop area than screen
disable fractional scale--> 100% and not responding at all
ctrl+alt+f1 -->login screen/login --> 200% and larger desktop area than screen, responding
trying again
200%-->100% black screen
ctrl+alt+f1 -->login screen/login --> black screen again
ctrl+alt+f1 -->login screen/login -->200% and larger desktop area than screen, responding
reboot--> 200%, normal desktop area
200%-->100% ok
-------------
On ubuntu 19.10, every fractional scale value is ok exept from video playing. Apps tested fail on full screen:
videos on youtube through firefox, smplayer, vlc: normal window->ok, maximize->ok, full screen->black
ps. If there is anything I can test, as far as I understand how to do it, I'll be glad to do it.
no longer affects: | nvidia-graphics-drivers (Ubuntu) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Zrimal (prabodha007) wrote : | #52 |
I found out nvidia_drm modeset parameter was not enabled correctly even if I enabled it in a/etc/modprode.d/ config file (options nvidia-drm modeset=1).
sudo cat /sys/module/
N
But after adding nvidia_
But still affected by https:/
Ubuntu 20.04 LTS
GeForce GTX 1050 Mobile
Dell XPS 9560
nvidia-driver-440 (440.82+
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #53 |
Thanks for your comments, but please note we do not officially support nvidia_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel Seymour (firstofth300) wrote : | #54 |
@vangugt
What's the status on when the fix will be released? We all see that you seem to have confirmed that the issue is no longer present with a new version, but none of us seem to have the version yet.
summary: |
- [nvidia] Screen scaling 125% gives 200% + [nvidia] Screen scaling 125% gives 200%, and sometimes extends off + screen |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : Re: [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen | #55 |
I just upgrade these following packages an hour ago but the issue seem to be not fixed:
linux-
linux-
linux-
linux-
As you can see, we have linux-modules-
summary: |
- [nvidia] Screen scaling 125% gives 200%, and sometimes extends off - screen + [nvidia] Screen scaling 125% gives 200% |
Changed in mutter (Ubuntu): | |
importance: | Undecided → Medium |
Changed in gnome-control-center (Ubuntu): | |
importance: | Undecided → Medium |
Changed in mutter (Ubuntu): | |
importance: | Medium → High |
Changed in gnome-control-center (Ubuntu): | |
importance: | Medium → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
James Joseph (jaayjay) wrote : | #57 |
Also affected by this bug, running vanilla 20.04 with Nvidia standard drivers
Nvidia version: 440.64
When turning on fractional scaling it defaults to 200% and zooms in on the screen and I can't change it down to 125% or 150% at all.
My work around for now is just to use 1440p rather then 4k resolution. Would be great to have this fixed in the future but it's not massively impairing me.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #58 |
On hold. I am waiting for Marco to finish work on some more general bugs in the randr scaling patch: bug 1876894 (which probably also affects bug 1875285), bug 1874207, bug 1873052. When those fixes are done and he's no longer working in the same area I will come back to this bug.
Changed in mutter (Ubuntu): | |
status: | In Progress → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kristo Ojasaar (kristoo) wrote : | #59 |
As a temporary fix, I found that you can scale the font size under Gnome Tweaks -> Fonts. Setting the scaling factor to 1.25 seems to work well for me, practically can't tell the difference.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #60 |
Yes indeed, I forgot about that. That will only scale fonts and not graphics. If you are OK with the slight disproportion that results in then that will also avoid randr scaling bugs like this one. Plus it will retain native performance levels.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : | #61 |
@kristoo: You know, the fact is we usually use more than one monitor (built-in monitor and external). Then we want only built-in monitor be scaled cause of available of big size that external monitor have.
After all, this bug should be fixed ASAP!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #62 |
ubuntu 19.10 just upgraded to 20.04 through update-manager.
Just after install and reboot-->black unusable
ctrl+alt+f1 --> login --> black unusable again
ctrl+alt+f3 --> terminal login --> remove nvidia* --> everything ok
normal login --> reinstall nvidia through additional drivers, reboot -->black unusable
ctrl+alt+f3 --> terminal login --> gsettings reset org.gnome.mutter experimental-
reboot--> black unusable--> ctrl+alt+f3 --> terminal login --> remove nvidia-settings--> reboot -->ok: now fractional scaling turning monitor to black for some time and everything goes back to 100% or 200% (depends the start point)
enabling fractional scaling again goes auto 200%-->100% and turn off fractional scaling goes auto back 100%-->200%
BUT with no nvidia-settings there is no extend off screen and there is no freeze on scale changes
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #63 |
Affected as well:
Ubuntu 20.04 LTS
GeForce MX150
NVIDIA-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Prashanth Shetty (prashetty) wrote : | #64 |
Having same Issue
Ubuntu 20.04 LTS
Operating System: Linux-x86_64
NVIDIA Driver Version: 440.64
GeForce GTX 960M
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Timo (timotimosn) wrote : | #65 |
Having the same issue...
But the tmp fix, posted by kristo on 2020-05-06 works great for me too: Browsers, my IDE (Intellij Idea), Slack, Thunderbird, the terminal, they all scale very well.
I increased the size of the mouse pointer, the dock icons and the icons in nautilus as well. As Daniel wrote on 2020-05-07 the performance is even better compared with fractional scaling activated.
But it has some downsides. From my point of view the most annoying one: these settings cannot be configured per display but only globally. @Daniel would it be possible to make the settings, mentioned above per display? It might be a more stable way if the performance issues and bugs, related to xrandr and Xorg in general, might occur again with every new nvidia graphic card model or new driver.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jack Kelly (jack-list) wrote : | #66 |
I agree with Timo: It'd be great to be able to set font size per screen! I might actually prefer that to screen scaling :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
obobo (ben-autonomic) wrote : | #67 |
The same (?)/similar issue using multi-monitor setup with GeForce GTX 1650 Mobile/Max-Q on a Dell XPS 15.
The screen on the external monitor appears to scale up proportionally beyond the viewport when using fractional scaling, so it is more as if the screen is zooming down into a portion of the desktop/application space.
Once this happens, everything goes crazy. It's impossible to get the screen resolutions back into a working condition without a reboot.
Having just been persuaded that everything's sunshine in the Linux world - after a decades break in OSX - I was so looking forward to the basics just working :-D
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Inakitajes (inakitajes) wrote : | #68 |
Affected as well
Dual 4k monitors
Geforce GTX 1660 OC
Ubuntu 20.04
Nvidia driver 440
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
obobo (ben-autonomic) wrote : | #69 |
I should probably mention that I'm also using a 4k UHD external display. I am seeing the same effect using the noveau drivers as the NVIDIA drivers (although, using the NVIDIA drivers the entire system occasionally and randomly hangs, but that's probably (?) unrelated).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
gamito (jorge-gamito) wrote : | #70 |
Also affected by this.
Huge bummer.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
vaughn (vaughnd) wrote : | #71 |
Still can't use different scales on my monitors. Need to set 125% on my 32" and 150% on my 43", but it freaks out even with the update on the proposed channel. Still have to set 150% only on the 32", let it jump both monitors to 200%, then tweak it in nvidia-settings.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Denis (dinvlad) wrote : Re: [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200% | #72 |
Running into this on a single 4k monitor with 125%, which worked well on
19.10. Now with 20.04, every time I click on 125% it will show the “zoomed
in” portion of the screen instead (so when I move mouse to the edges of the
screen, it “slides” the viewport towards that instead). In addition, it
doesn’t preserve the 125% setting as others mentioned. Using proprietary
Nvidia driver.
On Thu, May 14, 2020 at 5:35 AM vaughn <email address hidden> wrote:
> Still can't use different scales on my monitors. Need to set 125% on my
> 32" and 150% on my 43", but it freaks out even with the update on the
> proposed channel. Still have to set 150% only on the 32", let it jump
> both monitors to 200%, then tweak it in nvidia-settings.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> Status in gnome-control-
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Procedure used:
> 1.
> Fully updated system via apt update && apt upgrade
>
> 2.
> Select the screen setup in gnome control center
>
> 3.
> Click the "Fractional scaling" toggle
>
> 4.
> Select 125% and click the green "use" button top right (it says "Anvend"
> in dansih)
>
> 5.
> Observe that the window has grown a lot, click the "use new settings"
> button
>
> 6.
> The window tells me, I am at 200% scaling. The "200%" option is now
> highlighted.
>
> 7.
> Switch back to 100% and file this bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubuntu-
> ProcVersionSign
> Uname: Linux 5.4.0-21-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 4 09:42:34 2020
> InstallationDate: Installed on 2018-01-14 (810 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
> PackageArchitec
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_
> LANG=da_DK.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-
> Symptom: release-upgrade
> UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joachim Wolff (joachimwolff) wrote : | #73 |
As workaround for those with just one monitor (or many but the same size), I tried what Kristo Ojasaar (kristoo) already suggested and I found something even simpler. There is no needs for the 'Tweak'-tool: For a 4k monitor, set it to 100% and go to Settings -> Universal Access and activate 'large text'. Now the 'scaling' is more or less what 125% under Ubuntu 19.10 used to be.
Seeing something so simple solving this, I wonder why the developers do not a define a css style-sheet (or however the gui colors / font size etc are defined) for the different scaling options and apply these as soon e.g. '125%' scaling is activated.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Denis (dinvlad) wrote : | #74 |
I tried text trick already, but unfortunately it doesn’t really solve the
problem. All of the regular UI elements (icons etc) remain tiny. I would
really suggest if we could please not go that route, and instead focus on
fixing the scaling properly, if possible.
On Thu, May 14, 2020 at 10:35 AM Joachim Wolff <email address hidden>
wrote:
> As workaround for those with just one monitor (or many but the same
> size), I tried what Kristo Ojasaar (kristoo) already suggested and I
> found something even simpler. There is no needs for the 'Tweak'-tool:
> For a 4k monitor, set it to 100% and go to Settings -> Universal Access
> and activate 'large text'. Now the 'scaling' is more or less what 125%
> under Ubuntu 19.10 used to be.
>
> Seeing something so simple solving this, I wonder why the developers do
> not a define a css style-sheet (or however the gui colors / font size
> etc are defined) for the different scaling options and apply these as
> soon e.g. '125%' scaling is activated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> Status in gnome-control-
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Procedure used:
> 1.
> Fully updated system via apt update && apt upgrade
>
> 2.
> Select the screen setup in gnome control center
>
> 3.
> Click the "Fractional scaling" toggle
>
> 4.
> Select 125% and click the green "use" button top right (it says "Anvend"
> in dansih)
>
> 5.
> Observe that the window has grown a lot, click the "use new settings"
> button
>
> 6.
> The window tells me, I am at 200% scaling. The "200%" option is now
> highlighted.
>
> 7.
> Switch back to 100% and file this bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubuntu-
> ProcVersionSign
> Uname: Linux 5.4.0-21-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 4 09:42:34 2020
> InstallationDate: Installed on 2018-01-14 (810 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
> PackageArchitec
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_
> LANG=da_DK.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-
> Symptom: release-upgrade
> UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ananya Nayan Borah (ananyanayan) wrote : | #75 |
I am facing the same problem.
Nvidia Geforce 940MX/Driver Version: 440.64 .
I tried xrandr scaling but it just throws part of the desktop out of the screen. I have a setup of 2 monitors one with 1920x1080 and one with 1366x768. It would be great if we can have fractional scaling seperately for seperate monitors because on my laptop its really small and its huge on the monitor. I tried the workaround provided by @Kristo it works to an extent but doesn't really solve everything; still its better to have something than nothing. I am new to ubuntu, could someone help me if there is any way to manipulate icon size seperately for different monitors?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesper de Jong (jespdj) wrote : | #76 |
This was working fine with the initial release of Focal Fossa, but has stopped working since a recent update on my Dell XPS 15.
It's an older model (2014) with 3200x1800 screen. I was using 175% scaling but now it seems to scale everything to 200%, and the Gnome top bar is too long so the icons on the top right are not visible anymore.
This laptop has both Intel and NVidia graphics. The NVidia X Server Settings app tells me I have NVidia driver version 390.132 - so it looks like this does not just happen with NVidia driver 440.64.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
teimcrr (marco-carrarini) wrote : | #77 |
Ubuntu 20.04, nVidia 1060, Dell 2715P 4k
The following settings work for me:
In Display Settings:
Scale: 200%
Fractional scaling: OFF
In nVidia settings -> xserver display configuration -> advanced
ViewPortIn 5120x2880
ViewPortOut 3840x2160+0+0
Panning: 5120x2880
Save to X configuration file
It gives me 150% scaling and it survives reboot
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesper de Jong (jespdj) wrote : | #78 |
It does have something to do with the NVidia graphics.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jesper de Jong (jespdj) wrote : | #79 |
In NVidia X Server Settings, I can switch to Intel graphics. When I do this and reboot, then fractional scaling works correctly. With NVidia graphics enabled, it does not work correctly.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Faraz Khan (farazrkhan) wrote : | #80 |
@Teimcrr: YOU are a life saver. The viewport hack works amazingly well
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #81 |
Sounds like a good workaround. That's what the Randr fractional scaling patch is *meant* to do.
I think you can hack/script those same settings with:
xrandr --fb WIDTHxHEIGHT
or
xrandr --output OUTPUT --scale-from WIDTHxHEIGHT
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
teimcrr (marco-carrarini) wrote : | #82 |
Yes, but expect some glitches in apps.
In Darktable for example, when hovering on gui elements, tooltips appear somewhere else in the screen...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : | #83 |
For temporation, I have just switch to Intel Onboard GPU, the fractional scaling work perfectly but the monitor seem to be lag a bit.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #84 |
Yeah that sounds like bug 1846398. If you are able to switch to Intel graphics then consider logging into 'Ubuntu on Wayland' instead.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Diego Lineros (diegolineros) wrote : | #85 |
The problem here is no the scaling itself, the problem here is being able to separate screens configurations, fractional or not. You must be able to set font sizes, scale, backgrounds, resolutions, etc, per screen in an independent way.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
red72 (red72) wrote : | #86 |
I have a Thinkpad T470p with a GeForce 940MX and I had the same scaling problem. I got my 150% and 175% scaling to work by changing the "PowerMizer Setting preferred mode" to "Auto" and "Select the GPU you would like to use" to "NVIDIA On-Demand". I changed then both at the same time so I am not sure if they both need to be changed or if just one did the trick. But my scaling is working now so I am happy.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alex (agwin) wrote : | #87 |
This also seems to be an issue when trying to set displays to something other than landscape, when I set my other monitor to portrait mode it stops displaying and my other screen "zooms" in like others are reporting. I have one 1440p and 4k, so the scaling issue also effects me along side this issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #88 |
Diego, that is bug 1857383, not this one.
Alex, that sounds like bug 1875285 and bug 1874217, not this one. But yes I can see there will be some confusion between bug 1875285 and here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel van Vugt (vanvugt) wrote : | #89 |
It sounds like bug 1875285 was also experienced by the original reporter here...
Strictly speaking I intended for this bug to be more about "Selecting scale 125% highlights 200% but actually renders at 100% still". Bug 1875285 will definitely confuse the matter though, as the screen may literally scale up 200%. That's a separate bug which you might experience at the same time :S
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Prashant Deva (prashant-deva) wrote : | #90 |
seeing same issue with gtx 1080 after upgrading to ubuntu 20.04. worked fine in 19.10
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ilovebytes (ilovebytes) wrote : | #91 |
hmm this bug was introduced here 1 month before the release of 20.4 and now a month after the release the bug is still there...
that's somehow quite a bit of a downer, at least for me :(
i know the devs always have a lot of work to do, but is there at least a light at the end of the tunnel ? can we expect a solution to this bug anytime soon ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ovidiu Parvu (ovidiuparvu) wrote : | #92 |
Seeing same issue with Ubuntu 20.04, GeForce GTX 1660 SUPER, NVIDIA driver 440.64. Used to work as expected in 19.10.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mitesh Shah (teshy) wrote : | #93 |
With a fresh install of Ubuntu 20.04 (downloaded ISO and installed one day after release of 20.04) fractional scaling with the Nvidia driver was working fine. It was still working fine after several updates, however, I think with the update to version 440 of the driver, fractional scaling stopped working correctly. I have configured the system to use another graphics adapter just to get the fractional scaling I need, but the performance difference is quite evident and I would prefer to use the Nvidia adapter.
I am searching on the internet for ways to revert to a previous version of the Nvidia driver. If anyone has done this successfully then I would really appreciate the steps required for this.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #94 |
@teshy I am on nvidia 435.21 and still I have the same problem. No need to revert the driver as it wont fix it.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mitesh Shah (teshy) wrote : | #95 |
@mastorak, thanks. I will carry on using my alternative adapter until a resolution is found for the issue.
I was able to downgrade to 390 and I still had the same problem, which confirms what you have written.
This affects me also:
Ubuntu 20.04, all the latest updates
GeForce MX150
Nvidia driver v440
Display 1 - built-in 1920 x 1080 15.2"
Display 2 - HDMI 1920 x 1080 24"
@vanvugt we're still waiting for the fix!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jorge Villavicencio (jorge-a-villavicencio) wrote : | #97 |
RTX 2080, same problem
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Estevão Dominique Dias (estevaodrdias) wrote : | #98 |
After more than one month, what is the state of this bug?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
staycalm (staycalm) wrote : | #99 |
Same here with a RTX 2070 Super.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luka Maljic (lmalj) wrote : | #100 |
RTX 2060 also. Any status updates?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Juan C. (juancroldan) wrote : | #101 |
Same issue with GeForce 920M with nvidia drivers (ASUS TP-300LJ).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
cynicalsomething (cynicalsomething) wrote : | #102 |
Also experiencing this bug with an RTX 2070 Super
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Evgeni Tsvetanov (ecvetanov) wrote : | #103 |
Experiencing this with RTX 2070 Super. Driver: 440.64. Using 3 monitors (two 4k, and one 1440). When I try to switch to 125% scaling for the 4k monitors I get all sorts of weird behavior: monitors disabling, low fps (the ubuntu UI is very laggy, behaves like it runs in 20-30 fps), weird zoom issue (hard to explain but when it happens the monitor is not the entire viewport and when I put the mouse close to the edge it moves the viewport).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Juan C. (juancroldan) wrote : | #104 |
I'm able to switch to 125% after switching to nouveau driver and restarting. The only issue I'm experiencing is a smaller cursor when using snap' Telegram Desktop, but it seems to be a bug on their side.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #105 |
Dear experts ,we're still waiting for the fix -(
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matt Hurd (matthurd) wrote : | #106 |
Confirmed bug on 20.04 with Nvidia 440 here too on 970M. Noveau works fine but the tablet is pretty unusable slow, so have to use NV440 with an uncomfortable resolution on the main screen :-(
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David O Neill (dmzoneill) wrote : | #107 |
Worked for me, require reboot, but then you can do fractional scaling
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David O Neill (dmzoneill) wrote : | #108 |
Worked for me, require reboot, but then you can do fractional scaling
https:/
root@dave-
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Oleg "Nightwing" Lomakin (nightwing666) wrote : | #109 |
This option work only with hybrid graphics. If you select "NVIDIA On-Demand" all will run on intel\amd integrated GPU(but you can run selected app on nvidia discrete GPU).
Without integrated GPU this workaround don't work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bazinac (kuceravej) wrote : | #110 |
I have this issue as well with drivers 440.64, it is really annoying.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alexander Bolshakov (alpharder) wrote : | #111 |
As for me this advertised feature of 20.04 was the main factor to install this OS on my hardware, because previous 3 years the lack of this feature prevented me from using Ubuntu.
Sadly, this bug affects me too - I am using Nvidia RTX 2070 Super together with Asrock X570 Taichi and Ryzen 3600.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erik Herlé (erik-herle) wrote : | #112 |
I am affected by this bug as well. My setup:
- Ubuntu 20.04 fresh install
- Nvidia drivers 435 & 440 (multiple re-installs)
- Nvidia GeForce GTX 1050 Ti
- Philips 328P6JV 4K 32" monitor
Strange enough, fractional scaling works fine when I run Ubuntu 20.04 as a virtual machine (VMware) on the same Windows 10 PC.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Djerk Geurts (djerkg) wrote : | #113 |
Very annoying bug as when selecting on-demand some things don't work (don't ask, my kid plays Minecraft on this laptop) which fails in on-demand mode. Selecting Nvidia as the main GPU I lose fractional scaling...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Justin S (ambientrevolution) wrote : | #114 |
This affects me too, external monitors only work when using the Nvidia card exclusively on my laptop, so fractional scaling is a must, but it just flickers and selects 200% instead.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #115 |
Noveau fractional scaling is fine, but pc works on slow motion..
marco-carrarini's solution seems perfect in the beginning, but many apps do not work as they should.. so I used to change to default while using such an app and return to the solution elsewhere. But after a while I dismiss the solution.
Now I am just waiting the fix while running the temporary solution of 1.25 font scale.
Maybe users with nvidia and hidpi shouldn't move forward from 19.10 (fractional scaling worked fine).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Egor Rudkov (gren236) wrote : | #116 |
Affects me as well:
- Ubuntu 20.04
- Nvidia driver 440
- Nvidia GeForce RTX 2060 Super
- 2 monitors: 2k and 1080p
I have a strange behaviour with this one. If I set my primary 2k display scaled to 125% and position my second 1080p monitor on the right - it works fine. But if I drag secondary monitor to the left from my primary one, I get this bug and mirroring turns on instead of join.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David Hlacik (hlacik) wrote : | #117 |
Everyone with Nvidia Driver is affected. In all Ubuntu 20.04 derivates. Thats it. Only think that is sad, that no one from DEVS seems to care.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mehmet Yildiz (mbits94) wrote : | #118 |
Yep same here:
- Ubuntu 20.04 (fresh install)
- Nvidia driver 440
- Geforce GTX 960
- iiyama 4k monitor
125% / 150% etc jumps to 200% after saving.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #119 |
I've tested this in a laptop with Nvidia GeForce GTX 1050 (and so PRIME), now in this scenario I don't get any scaling at all using
xrandr --output eDP-1 --scale 1.25x1.25 # replace eDP-1 with your output
But an extended desktop instead.
So these are two different issues.
Who is affected, can please check this again (use this command to reset xrandr --output eDP-1 --scale 1x1), and let us know what happens and what graphic card is used?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #120 |
@3v1n0
NVIDIA GeForce GTX 1050 Ti
I 've used a single 3840x2160 screen connected to the GPU
After resetting, then using: xrandr --output HDMI-0 --scale 1.25x1.25
zooms out the screen by 25%
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #121 |
@mastorak
That's not a mobile card, isn't it?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #122 |
I've uploaded some test packages this ppa:
https:/
Try them with:
sudo add-apt-repository ci-train-
I'm quite sure they don't solve this issue, but with them I should get some better debug information.
So please, once installed and restarted your session (or Alt+f2 -> 'r' -> enter to restart the shell only):
- Run this in a terminal:
journalctl /usr/bin/
- change your settings to a fractional value from g-c-c
- attach here the journalctl output (with the outcome)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
se4n (leogouv) wrote : | #123 |
@3v1n0
That worked for me...
- Ubuntu 20.04
- NVIDIA driver 440
- NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
jun 23 10:37:54 se4n-lx gnome-shell[2514]: GNOME Shell started at Tue Jun 23 2020 10:37:50 GMT-0300 (-03)
jun 23 10:37:54 se4n-lx gnome-shell[2514]: Registering session with GDM
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Received error from D-Bus search provider org.gnome.
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Wrong number of result metas returned by search provider org.gnome.
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Received error from D-Bus search provider org.gnome.
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Wrong number of result metas returned by search provider org.gnome.
jun 23 10:38:18 se4n-lx gnome-shell[2514]: Received error from D-Bus search provider org.gnome.
jun 23 10:38:18 se4n-lx gnome-shell[2514]: Wrong number of result metas returned by search provider org.gnome.
jun 23 10:38:30 se4n-lx gnome-shell[2514]: Enabling experimental feature 'x11-randr-
jun 23 10:38:30 se4n-lx gnome-shell[2514]: Setting screen size 3840x2160
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('DP-2', '3840x2160@
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('DP-2', '3840x2160@
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('DP-2', '3840x2160@
jun 23 10:38:38 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('DP-2', '3840x2160@
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Crtc at 0,000000x0,000000 size 3072,000000x172
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size 6144x3456
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size to 6144x3456
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Scaling at 0,625000 (transformation matrix is 104857 = 1,599991) using filter good
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Configuring CRTC 441 with mode 450 (3840 x 2160 @ 59,996624) at position 0, 0 and transform 0
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting UBUNTU cr...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitaly Sulimov (vsulimov) wrote : | #124 |
@3v1n0
xrandr also command doesn't work for me (laptop with GeForce MX250 and Intel GPU). Getting extended desktop instead of scaling as you mention in #119
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ThOR27 (thor27-gmail) wrote : | #125 |
Hi, tried the new package, it didn't fixed, changed 100% to 125% and it scaled to 200%. The output of the mentioned command:
jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@
jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@
jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Crtc at 0,000000x0,000000 size 2752,000000x115
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size 5504x2304
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size to 5504x2304
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Scaling at 0,625000 (transformation matrix is 104857 = 1,599991) using filter good
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Configuring CRTC 633 with mode 640 (3440 x 1440 @ 59,972618) at position 0, 0 and transform 0
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting UBUNTU crtc config crtc 633, timestamp 0 (config timestamp 319695), x: 0, y: 0, mode: 640, rotation 1, n_outputs 1: RETURN reply 0x5650ad5b5ea0, error: (nil)
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size 5504x2304
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #126 |
- mutter.log Edit (49.7 KiB, text/plain)
@3v1n0
It is desktop GPU.
I tried the new mutter package. It doesn't fix the problem.
The behavior now is the following:
-enable fractional scaling
-select and apply 125%
-goes to 200%
-select to go back to to 100%
-things are tiny again but the desktop pixels have increased beyond the borders of the screen so you have to scroll to view the rest of the desktop.
When going from 100% to 200% and back to 100% -without- enabling fractional scaling going back to 100% behaves correctly.
Please find attached the log.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #127 |
It would be good to find out how we get HiDPI displays to the testing team, because this should not have made it past test.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #128 |
@mastorak: are you sure you're using those packages?
I don't see any reference in the logs.
@blitmaps, most of the developers use intel or free drivers all the time, so testing in other scenarios is not always possible.
Also this bug has at least three different behaviors depending on GPU hardware, for example in my Prime hardware it behaves correctly, while it doesn't in another prime hardware I recently got.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #129 |
- new_mutter.log Edit (9.3 KiB, text/plain)
@3v1n0
You are indeed right. The new mutter package was not installed from the ppa for some reason.
I think it should be ok now. Version is 3.36.3-
I am happy to report that fractional scaling works now. Compositor behavior seems a bit weird(as if there is more tearing) when moving windows but that just might be my idea.
Please find attached the new logs
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #130 |
@3v1n0
I did some further testing with your mutter package and noticed some important issues. Even though scaling works mostly ok, I noticed a consistent side-effect on X applications that they scale in reverse to the rest of the UI. So Gnome Shell, GTK apps and QT apps will scale 125% but at the same time X apps will scale 0.75% (or lower) and they ll become super tiny. You can test this with Gimp xterm and XNethack.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Serghei Iakovlev (i.serghei) wrote : | #131 |
- gnome-shell logs Edit (4.1 KiB, text/plain)
Hello @3v1n0
Still no luck. I added ci-train-
Bellow some info of my hardware:
$ inxi -G
Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 440.100
Display: x11 server: X.Org 1.20.8 driver: nvidia unloaded: fbdev,modesetti
OpenGL: renderer: GeForce GTX 1080/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100
$ lshw -c video
*-display
description: VGA compatible controller
product: GP104 [GeForce GTX 1080]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:06:00.0
version: a1
width: 64 bits
clock: 33MHz
resources: irq:66 memory:
$ lspci | egrep -i vid\|vga
06:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
06:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
3840x2160 60.00*+ 59.94 50.00 30.00 29.97 25.00 23.98
2560x1440 59.95
1920x1080 60.00 59.94 50.00 29.97 23.98
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1280x720 60.00 59.94
1152x864 60.00
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 59.94
640x480 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David (mobilebackup) wrote : | #132 |
- journal control output Edit (14.3 KiB, text/plain)
I tried the new ppa package. I could at least change the value of the fractional to 175% and 125% without crashing the system. Previously, my system would just go black screen and I had to login using text and remove all gnome settings manually (cd ~ && rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/
I am attaching the journal ctl log. Currently I am at 175% scaling and will use it and see if other things are problematic. I still think that on high resolution displays with nvidia (laptops), the UI needs testing and change. The ratio of the text size vs icon size etc need tweaking for better defaults.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #133 |
- log as requested Edit (32.5 KiB, text/plain)
@Treviño
Your ppa work for me in terms of proportional, fractional scaling to 125%.
My configuration is Ubuntu 20.04 x86_64
GeForce GTX 1060
440 tested driver
Log attached - Thank you for your work on this.
Text aliasing is not correct, there is some sub-pixel bulging that appears like a larger texture area is being rendered and scaled down incorrectly (perhaps bilinear scaling down to the output resolution). If this is the case, it is a good workaround, but not suitable for professional workflows. If we know roughly what the issue is, I am happy to test/look at code etc.
Re: my comment about this not getting past test. If the testers are using a different driver set, then to say the (prop) drivers are tested is not really representative; I know a lot of people are donating their time, and I know we can't test all the configurations - but this is core functionality.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Filippo Argiolas (fargiolas) wrote : | #134 |
- mutter.log Edit (13.9 KiB, text/plain)
@3v1n0
With your ppa fractional scaling works again (I'm almost sure it worked fine in 19.10)
Text rendering is pretty bad at 125%, slightly better at 150%
Geforce GTX 1080, latest nvidia driver (440.100), Philips 328P 4k display.
Thanks for looking into this, let me know if I can do more.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David (mobilebackup) wrote : | #135 |
I think there is another problem, perhaps related. When I get to 175% scaling, and I try to use gnome-tweaks or dconf-editor, my font sizes don't seem to change at all. The fonts are tiny on my screen.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alex (agwin) wrote : | #136 |
The scaling issue was fixed for me, now I can independently scale monitors, but if I try to change a monitor to portrait mode it fails and I get the issue with incorrect zoom and overlapping view ports.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #137 |
The problems you are experiencing @mobilebackup and @agwin, are most likely due to the way the workaround works. Correct me if I am wrong, but the workaround is asking the graphics system to render a larger canvas (say 2x, 8K or whatever) and scales this down to the viewport size. If an application is not enabled for HiDPI mode, they will be very squished. If you don't have sqaure pixels (like most of us), you will get bad text, and if you don't check for orientation, the viewport will break.
The reason I said this is a fab workaround, but won't hold for production, apart from above, is we are asking the card to render a huge area. If you move windows around or watch video with GPU decoding, the card is going to have to move a huge amount of data around.
These are my ramblings, for whatever they are worth.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David (mobilebackup) wrote : | #138 |
@blitmaps I think its not as simple as that. It seems that the current state of things, (I'm on a 4k) - I am not even talking about hidpi mode supporting applications - even Gnome acts wierd. For example there is no reason for the titlebar font not to update in size?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #139 |
@mobilebackup - agreed that there are going to be lots of problems this workaround will not solve. It is not yet clear whether any 'weirdness' is caused by the original bug or the workaround.
With regards to the title bar, I am using the default gnome theme, with 'Larger Text' enabled in universal access. This seems to work with most applications; however, in CLion and other Jetbrains IDE's im having to set the font size to 48 to make it readable, as it does its own rendering. Are you using a theme that renders its fonts for example? or are you using a default theme?
Also, what other wierdness are you experiencing - I am getting lagginess and jittering - however this is mostly when changing large amounts of the screen (hense the comment about large rendering areas).
Sorry I'm not of more help, I would like to be, but the rendering stack is a monolith - I was commenting on past experience of rendering larger areas and scaling down (it doesn't work very well); that said, I can currently do work on my configuration.
Apologies for more ramblings, if they are not helpful.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David (mobilebackup) wrote : | #140 |
Thanks for the help @blitmaps. Indeed the universal access helped with the larger font size. Lets hope Ubuntu's gnome stabalizes on 4k/+ monitors soon with nvidia. That is a large population of users.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Roger Hunwicks (roger-tonic-solutions) wrote : | #141 |
The working around is working adequately for me:
Jul 02 08:50:59 lenny gnome-shell[17639]: Enabling experimental feature 'x11-randr-
Jul 02 08:50:59 lenny gnome-shell[17639]: Crtc at 0.000000x2160.
Jul 02 08:50:59 lenny gnome-shell[17639]: Crtc at 0.000000x0.000000 size 1920.000000x108
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting screen size to 3840x4320
Jul 02 08:50:59 lenny gnome-shell[17639]: Scaling at 1.000000 (transformation matrix is 65536 = 1.000000) using filter fast
Jul 02 08:50:59 lenny gnome-shell[17639]: Configuring CRTC 504 with mode 509 (3840 x 2160 @ 59.999294) at position 0, 2160 and transform 0
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting UBUNTU crtc config crtc 504, timestamp 0 (config timestamp 158041), x: 0, y: 2160, mode: 509, rotation 1, n_outputs 1: RETURN reply 0x56264b3d7970, error: (nil)
Jul 02 08:50:59 lenny gnome-shell[17639]: Scaling at 1.000000 (transformation matrix is 65536 = 1.000000) using filter fast
Jul 02 08:50:59 lenny gnome-shell[17639]: Configuring CRTC 441 with mode 448 (3840 x 2160 @ 60.000000) at position 0, 0 and transform 0
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting UBUNTU crtc config crtc 441, timestamp 0 (config timestamp 158041), x: 0, y: 0, mode: 448, rotation 1, n_outputs 1: RETURN reply 0x56264b3d7970, error: (nil)
Jul 02 08:51:00 lenny gnome-shell[17639]: Unset XDG_SESSION_ID, getCurrentSessi
Jul 02 08:51:00 lenny gnome-shell[17639]: Will monitor session 2
Jul 02 08:51:00 lenny gnome-shell[17639]: Telepathy is not available, chat integration will be disabled.
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Error looking up permission: GDBus.Error:
Jul 02 08:51:02 lenny gnome-shell[17639]: GNOME Shell started at Thu Jul 02 2020 08:51:00 GMT-0400 (EDT)
Jul 02 08:51:02 lenny gnome-shell[17639]: Registering session with GDM
Jul 02 08:52:08 lenny gnome-shell[17639]: polkitAuthentic
Jul 02 08:52:23 lenny gnome-shell[17639]: ../clutter/
Jul 02 08:52:28 lenny gnome-shell[17639]: GOt configuration change [(0, 2160, 1.0, uint32 0, false, [('eDP-1-1', '3840x2160@
Jul 02 08:52:29 lenny gnome-shell[17639]: GOt configura...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dmitry (r0ute) wrote : | #142 |
Worked for me too
Jul 03 15:39:40 pop-os gnome-shell[1517]: Crtc at 0.000000x0.000000 size 3840.000000x216
Jul 03 15:39:40 pop-os gnome-shell[1517]: Crtc at 3840.000000x0.
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:40 pop-os gnome-shell[1517]: Configuring CRTC 442 with mode 448 (3840 x 2160 @ 59.996624) at position 0, 0 and transform 0
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting UBUNTU crtc config crtc 442, timestamp 0 (config timestamp 13025), x: 0, y: 0, mode: 448, rotation 1, n_outputs 1: RETURN reply 0x55f93a90d600, error: (nil)
Jul 03 15:39:40 pop-os gnome-shell[1517]: Configuring CRTC 441 with mode 477 (1920 x 1200 @ 59.950172) at position 3840, 0 and transform 0
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting UBUNTU crtc config crtc 441, timestamp 0 (config timestamp 13025), x: 3840, y: 0, mode: 477, rotation 1, n_outputs 1: RETURN reply 0x55f93a90d6f0, error: (nil)
Jul 03 15:39:40 pop-os gnome-shell[1517]: Failed to load module "appmenu-
Jul 03 15:39:41 pop-os gnome-shell[1517]: Unset XDG_SESSION_ID, getCurrentSessi
Jul 03 15:39:41 pop-os gnome-shell[1517]: Will monitor session c1
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Unable to connect to ibus: Could not connect: Connection refused
Jul 03 15:39:41 pop-os gnome-shell[1517]: Error looking up permission: GDBus.Error:
Jul 03 15:39:41 pop-os gnome-shell[1517]: JS WARNING: [resource:
Jul 03 15:39:42 pop-os gnome-shell[1517]: Registering session with GDM
Jul 03 15:39:48 pop-os gnome-shell[2515]: Enabling experimental feature 'x11-randr-
Jul 03 15:39:48 pop-os gnome-shell[2515]: Failed to read monitors config file '/home/
Jul 03 15:39:48 pop-os gnome-shell[2515]: Crtc at 0.000000x0.000000 size 3840.000000x216
Jul 03 15:39:48 pop-os gnome-shell[2515]: Crtc at 3840.000000x0.
Jul 03 15:39:48 pop-os gnome-shell[2515]: Setting screen size 5760x2160
Jul 03 15:39:48 pop-os gnome-shell[2515]: Scaling at 1.000000 (transformation matrix is 65536 = 1.000000) using filter fast
Jul 03 15:39:48 pop-os gnome-shell[2515]: Configuring CRTC 442 with mode 448 (3840 x 2160 @ 59.996624) at position 0, 0 and transform 0
Jul 03 15:39:48 pop-os gnome-shell[2515]: Setting UBUNTU crtc config crtc 442, timestamp 0 (config timestamp 21095), x: 0, y: 0, mode: 448, rotation 1, n_outputs 1...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hongwen000 (hongwen000) wrote : | #143 |
sudo add-apt-repository ppa:ci-
worked for me.
GTX 750Ti, 440 driver
-- Logs begin at Mon 2020-07-06 19:24:15 CST. --
7月 06 20:12:56 lixinrui-ubuntu gnome-shell[1095]: Setting screen size 1440x900
7月 06 20:12:57 lixinrui-ubuntu gnome-shell[1095]: Unset XDG_SESSION_ID, getCurrentSessi
7月 06 20:12:57 lixinrui-ubuntu gnome-shell[1095]: Will monitor session c1
7月 06 20:12:58 lixinrui-ubuntu gnome-shell[1095]: Error looking up permission: GDBus.Error:
7月 06 20:12:59 lixinrui-ubuntu gnome-shell[1095]: JS WARNING: [resource:
7月 06 20:12:59 lixinrui-ubuntu gnome-shell[1095]: Getting invalid resource scale property
7月 06 20:13:00 lixinrui-ubuntu gnome-shell[1095]: Registering session with GDM
7月 06 20:13:04 lixinrui-ubuntu gnome-shell[1614]: Enabling experimental feature 'x11-randr-
7月 06 20:13:04 lixinrui-ubuntu gnome-shell[1614]: Setting screen size 1440x900
7月 06 20:13:05 lixinrui-ubuntu gnome-shell[1614]: Unset XDG_SESSION_ID, getCurrentSessi
7月 06 20:13:05 lixinrui-ubuntu gnome-shell[1614]: Will monitor session 2
7月 06 20:13:05 lixinrui-ubuntu gnome-shell[1614]: Telepathy is not available, chat integration will be disabled.
7月 06 20:13:06 lixinrui-ubuntu gnome-shell[1614]: Error looking up permission: GDBus.Error:
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
7月 06 20:13:08 lixinrui-ubuntu gnome-shell[1614]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
7月 06 20:13:09 lixinrui-ubuntu gnome-shell[1614]: GNOME Shell started at Mon Jul 06 2020 20:13:06 GMT+0800 (CST)
7月 06 20:13:09 lixinrui-ubuntu gnome-shell[1614]: Registering session with GDM
7月 06 20:13:16 lixinrui-ubuntu gnome-shell[1614]: GOt configuration change [(0, 0, 1.25, uint32 0,...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #144 |
"sudo add-apt-repository ppa:ci-
It doesn't work for me.
gtx1050ti, 440 driver
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dong Xuan Huy (huydx.evil) wrote : | #145 |
I just changed the subscriber status to "Notify me when this bug is closed"!
That a long long time waiting!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #146 |
It would be good to get a steer on what @vanvugt thinks the problem is, or if there are multiple problems?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #147 |
I've updated the package in the PPA mentioned at [1], so feel free to test the packages again.
These should not fix the problem for mobile cards, as those seems to have another problem at modesetting driver level, it seems.
For others, the issue seems to be related more to screen sizes that mutter sets, and the packages should address that, but not sure if that's valid for all the cards.
[1] https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #148 |
@3v1n0
NVidia 1050 Ti (Desktop)
435.21
The updated package is ok for me the Desktop Environment and most apps, but for some apps such as Gimp and XNethack the scale is inverted and their UI,icons,etc become tiny.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #149 |
- journalctl.log Edit (14.3 KiB, text/plain)
@3v1n0
NVidi MX150 (440)
The updated package not work for me.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #150 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #151 |
@3v1n0 - The updated package works for me.
20.04, GeForce GTX 1060. 440 drivers.
Nice work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ari (ari-reads) wrote : | #152 |
The updated package worked
20.04, GTX 1650
Driver 440.100
Monitor: 4K, 32".
This a new setup - the screen is large enough that 100% is kind of usable, although the GUI fonts of GTK apps (gnome shell, darktable) was in general too tiny - with the Trevino's patch I could now set the resolution to 125% but then found that the ubuntu GUI became too large.
Ideally, I noticed that a of 110% scale or so, like my mac does on the same screen, works best.
In case it helps anyone: if you prefer scaling at 100% but want larger fonts in most apps
Gnome Tweaks > Fonts > Scaling Factor = 1.1
Firefox > about:config > layout.
Terminal / Tilix > Fonts > Inconsolata 14px
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Geroen Dierckx (ridiekel) wrote : | #153 |
Ubuntu 20.04, RTX 2080
Driver 440.100
For me the update also works. However performance is not as I would expect (very choppy mouse movement). But that is probably a completely different problem. The update fixes the issue addressed here.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ThOR27 (thor27-gmail) wrote : | #154 |
- journalctl /usr/bin/gnome-shell -b0 -ef Edit (8.8 KiB, text/plain)
Update still does not work here, same behaviour as before (200% instead of 125%).
It's not a mobile GPU:
NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1)
NVIDIA Driver Version: 435.21
$ dpkg -l | grep mutter
ii gir1.2-
ii libmutter-6-0:amd64 3.36.3-
ii mutter 3.36.3-
ii mutter-common 3.36.3-
journalctl /usr/bin/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
cynicalsomething (cynicalsomething) wrote : | #155 |
I have the same experience as ridiekel. Fixes the issue reported, but performance takes a huge hit with a choppy mouse.
RTX 2070 Super
Driver 440.100
L Monitor: 1080
C Monitor: 4k
R Monitor: 4k
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Cristian (cristianrgreco) wrote : | #156 |
I have the same issue as thor27
$ sudo lshw -C display
*-display
description: VGA compatible controller
product: GK110B [GeForce GTX 780 Ti]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
resources: irq:57 memory:
$ dpkg -l | grep mutter
ii gir1.2-
ii libmutter-6-0:amd64 3.36.3-
ii mutter 3.36.3-
ii mutter-common 3.36.3-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dmitry (r0ute) wrote : | #157 |
After restart or recent update everything stopped working.
Jul 17 09:20:15 pop-os gnome-shell[1494]: Failed to load module "appmenu-
Jul 17 09:20:16 pop-os gnome-shell[1494]: Unset XDG_SESSION_ID, getCurrentSessi
Jul 17 09:20:16 pop-os gnome-shell[1494]: Will monitor session c1
Jul 17 09:20:16 pop-os gnome-shell[1494]: Error looking up permission: GDBus.Error:
Jul 17 09:20:16 pop-os gnome-shell[1494]: JS WARNING: [resource:
Jul 17 09:20:17 pop-os gnome-shell[1494]: Registering session with GDM
Jul 17 09:20:24 pop-os gnome-shell[2541]: Enabling experimental feature 'x11-randr-
Jul 17 09:20:24 pop-os gnome-shell[2541]: Failed to load module "appmenu-
Jul 17 09:20:24 pop-os gnome-shell[2541]: Unset XDG_SESSION_ID, getCurrentSessi
Jul 17 09:20:24 pop-os gnome-shell[2541]: Will monitor session 2
Jul 17 09:20:24 pop-os gnome-shell[2541]: Telepathy is not available, chat integration will be disabled.
Jul 17 09:20:24 pop-os gnome-shell[2541]: gnome-shell-
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: test for equality (==) mistyped as assignment (=)?
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: test for equality (==) mistyped as assignment (=)?
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: reference to undefined property 1
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: reference to undefined property 0
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: reference to undefined property "crypto"
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: g_file_
Jul 17 09:20:24 pop-os gnome-shell[2541]: JS WARNING: [/<email address hidden>/math.js 42]: reference to undefined property "-1"
Jul 17 09:20:25 pop-os gnome-shell[2541]: pop-shell: [INFO] init
Jul 17 09:20:25 pop-os gnome-shell[2541]: pop-shell: [INFO] enable
Ju...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alex (agwin) wrote : | #158 |
I had a 2080ti that died so I was running a 1070 until the RMA came, and the updated PPA worked perfectly with no issues. Swapped in the new 2080ti yesterday and have had a pretty significant performance hit since then, choppy movement and animations, feels like the whole desktop is running at 30fps or less. Same driver and other hardware.
Nvidia driver 440.100
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alex (agwin) wrote : | #159 |
Did some more testing, it does actually look like one of my monitors is running at 30hz instead of 60hz, although the settings are reporting that it is running at 60hz.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Diego Lineros (diegolineros) wrote : | #160 |
Forget about this, this setting it's and will be always broken, a white sheet will be needed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #161 |
Will those changes be merged into the 20.04.1 release?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willy Nolan (optonox) wrote : | #162 |
Hi,
I can't use fractional scaling at all. When I enable it from the Settings in Gnome it just loads for a while (flickering black screen) and then reverts to Single Display. Switching back to Join Displays does nothing and I have to unplug and plug the external monitor back in.
I am using "Nvidia Driver metapackage nvidia-driver-450" and "Ubuntu 20.04.1 LTS"
I have a RTX 2080
I am using a laptop with a 4K monitor and an external 4K monitor that is larger, so obviously I'd love to set different fractional scaling values per monitor but would settle for setting 150% for both.
This seems like a common use case. Please let me know how I can help.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew D. Mower (mdmower) wrote : | #163 |
@marco-carrarini In post #77, you suggested a workaround by modifying xorg.conf. Then in post #81, @vanvugt suggested the same outcome could be achieved with `xrandr --fb` or `xrandr --scale-from`. Finally, you responded in #82 with "Yes, but expect some glitches in apps."
I'm not clear if your response to "expect some glitches" was only for @vanvugt's xrandr suggestion, or if the two workarounds are equivalent and to "expect some glitches" with either method. Any clarification would be appreciated. Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alexandre Speltri (alexandreporks) wrote : | #164 |
I know that this isn't a good way of solving things, but after some months I realized that Pop_OS! 20.04 works with Fractional scaling+NVIDIA+X.
If someone is tired of waiting (like I was), it's worth a shot.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vincent Gerris (vgerris) wrote : | #165 |
I had this issue with an internal FHD screen on a Dell laptop with Nvidia MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external monitor at 150% and the laptop at 100%.
So a valid workaround for me, perhaps for others.
It's nice to see other workarounds too, I hope this bug will be fixed in a way that this works without any application/
I don't want to change font size, multiple settings across apps and such, just have a single point to change that works, just like in other major OSes :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David Hlacik (hlacik) wrote : | #166 |
@alexandreporks hows that possible? I am using Pop_OS 20.04 since it release date, and fractional scaling does not work , same as Ubuntu 20.04.
Could you please provide me with the steps? Did you just enable fractional scaling with gsettings set org.gnome.mutter experimental-
and it worked??
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alexandre Speltri (alexandreporks) wrote : | #167 |
@david-hlacik Well, until a month ago, yes. I had enabled the Experimental features and it just worked.
Some update broke that, so I had to manually add a simple command to "Startup Applications", which was: xrandr --output eDP-1-1 --scale 1.5x1.5
To complete the setup, I let the display scalling (from gnome settings) to 2x (200%).
There you go! It worked
For more info, see (https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willy Nolan (optonox) wrote : | #168 |
Daniel van Vugt: @vanvugt:
It is safe to say that, when using Nvidia drivers, the fractional scaling is completely broken.
- You can't set the scale differently on different monitors (basic functionality)
- The fractional scaling doesn't work at all (even if you set it to be the same for both or multiple monitors)
There are several (almost 50) different hardware configurations having this issue and there are several "workarounds" all of which have their own issues.
This is an extremely basic functionality and something that is needed as I have read that *the most common* way to work right now is a laptop with one external display. If using Nvidia drivers, that setup does not work.
Can you tell me how to get involved or what I can do to get this working? It has been several months and I'd like to solve this problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jaromir Obr (jaromir-obr) wrote : | #169 |
I have similar problem with AMD graphics Renoir (Is it the same problem as this issue #1870736 ?). I can scale display from 100% to 200%, but scaling to 125% or 150% fails (see log below).
At least I'm able to scale text to 1.25.
syslog:
-------
Aug 15 18:36:47 yoga gnome-shell[9538]: Impossible to set scaling on crtc 925 to 0,625000, error id 2
Aug 15 18:36:47 yoga gnome-shell[9538]: Window manager warning: Scalig CRTC 925 at 1,000000 failed
Used HW/SW:
-----------
* Lenovo Yoga Slim 7 14ARE05 (Ryzen 4700u, Integrated AMD Radeon Graphics),
* Ubuntu 20.04.1
$ lspci
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c2)
Kernel modules: amdgpu
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected primary 1920x1080+0+0 0mm x 0mm
1920x1080 77.00*
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jaromir Obr (jaromir-obr) wrote : | #170 |
I fixed the issue by installation of proprietary AMDGPU drivers (https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willy Nolan (optonox) wrote : | #171 |
This mess just goes on and on and on.
Can somebody provide an update on:
- What work is being done to get fractional scaling working on Ubuntu with nVidia cards?
- How someone who wants to help fix this required basic functionality would do so?
I don't think that read >170 posts just to scale a GUI is a good experience for users. It is unclear who is a user and who is actually an authority on the topic.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #172 |
@optonox, I think you will not get a satisfactory answer to your questions.
The issues that manifest this behaviour, as I understand it, are sprawling. The implementation of highDPI on the platform is quite naive, and fragmented due to the various packages handling the rendering, and the various UI libraries used to create the apps. That's before we get to driver vendors etc.
I'm just a user, and image processing/computer graphics is my full time job - I wouldn't know where to start contributing.
It is going to be a long, long road to a decent experience for High DPI screens and multiple DPI setups. That's my very unhelpful 2 pennies worth, hope it helps.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willy Nolan (optonox) wrote : | #173 |
Totally makes sense. It's just too bad as Microsoft Windows had this figured out several years ago. I want to do more than complain. I want to help fix this mess.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #174 |
It is finally fixed! <3
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willy Nolan (optonox) wrote : | #175 |
No it is not.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #176 |
Somehow after I updated through update-manager about an hour ago and restart, now it is working fine. I also notice a scroll bar on loginscreen (although I have only one user). After logged in, I notice the text (previous was 1.25) to seem a bit larger.. And I goto settings/monitor. Now (at least for me) fractional scaling is working.
What I tested:
100%->125%
125%->100%
125%->150%
150%->100%
and everything was as expected. What can I do to check it further?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Fusion (bornolbers) wrote : | #177 |
checked again every possible change.. (ecxept from 200%) and everything is working fine!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
August Oberhauser (gustl22) wrote : | #178 |
Fractional Scaling works for me after update.
NVIDIA Corporation GM204 [GeForce GTX 970]
Scrolling and 4K videos are very laggy in 125%, 150% and 175% mode.
Tested with:
- NVIDIA driver metapackage from nvidia-driver-440 (proprietary)
- NVIDIA driver metapackage from nvidia-driver-450 (open-source)
1 x 4K-Monitor (125%)
1 x FHD-Monitor (100%)
Used this command to see GPU usage:
$ watch -n 0.5 nvidia-smi
Watching 4k Video (120fps):
- no scaling: 25% capacity
- with scaling: 65% capacity (sometimes flickering and black screen)
No interaction:
- no scaling: 3% capacity
- with scaling: 6% capacity
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mehmet Yildiz (mbits94) wrote : | #179 |
Fractional scaling also works again for me after the update.
Only problem I now have is some freezing / lag when I watch 4k videos (e.g. via YouTube) I tried different browsers, 4K videos play a bit better on chrome (less lag) then on Firefox. Scrolling is also slow / laggy.
Did not have these issues with the workaround.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ThOR27 (thor27-gmail) wrote : | #180 |
Fractional scalling still not working for me at all. Same exactly behavior as before.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Geroen Dierckx (ridiekel) wrote : | #181 |
Happy to say that for that for me at least it works. No more choppy mouse movement and I am able to use both my monitors with the first in 150% and the second in 175%. I also tested playing some 4k movies in firefox, which worked fine.
DP-0 connected primary 5120x2880+0+0 (normal left inverted right x axis y axis) 698mm x 393mm
3840x2160 60.00*+ 59.94 50.00 29.98 29.97 25.00 23.98 23.98
...
DP-2 connected 4384x2466+5120+0 (normal left inverted right x axis y axis) 521mm x 293mm
3840x2160 60.00*+ 29.98
...
Thanks to all involved for fixing this issue!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
OB (treystoreau) wrote : | #182 |
How do I install the patch?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jipeng Tan (tan1986) wrote : | #183 |
I just did apt update && apt upgrade
Now fractional scaling is working.
ubuntu 20.04
nvidia 1070ti
nvidia-driver-440
On Sun, Aug 23, 2020 at 12:30 AM OB <email address hidden> wrote:
> How do I install the patch?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> Status in gnome-control-
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Procedure used:
> 1.
> Fully updated system via apt update && apt upgrade
>
> 2.
> Select the screen setup in gnome control center
>
> 3.
> Click the "Fractional scaling" toggle
>
> 4.
> Select 125% and click the green "use" button top right (it says "Anvend"
> in dansih)
>
> 5.
> Observe that the window has grown a lot, click the "use new settings"
> button
>
> 6.
> The window tells me, I am at 200% scaling. The "200%" option is now
> highlighted.
>
> 7.
> Switch back to 100% and file this bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubuntu-
> ProcVersionSign
> Uname: Linux 5.4.0-21-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 4 09:42:34 2020
> InstallationDate: Installed on 2018-01-14 (810 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
> PackageArchitec
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_
> LANG=da_DK.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-
> Symptom: release-upgrade
> UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Yousry Abdallah (yousry-abdallah) wrote : | #184 |
This problem still exists on my system (Latest Updates / Nvidia Titan).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #185 |
People with that still have the issue, can please give us:
- The card you're using (AFAIK mostly mobile cards are affected)
- The output of: apt-cache policy libmutter-6-0
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christians (script-vollbio) wrote : | #186 |
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce GTX 1050/PCIe/SSE2
GL_VERSION: 4.6.0 NVIDIA 440.100
apt-cache policy libmutter-6-0
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
500 http://
100 /var/lib/
3.
500 http://
I would LOVE to have that fixed!!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Djerk Geurts (djerkg) wrote : | #188 |
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
100 /var/lib/
3.
500 http://
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)
+------
| NVIDIA-SMI 390.138 Driver Version: 390.138 |
|------
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|======
| 0 Quadro K1100M Off | 00000000:01:00.0 Off | N/A |
| N/A 59C P0 N/A / N/A | 1460MiB / 1999MiB | 3% Default |
+------
I have both discreet and Nvidia. I'd like to use the Nvidia on demand,
but there's an issue with prime that I had so I'm on Nvidia permanently
at the moment.
On 24/08/2020 15:41, Marco Trevisan (Treviño) wrote:
> People with that still have the issue, can please give us:
> - The card you're using (AFAIK mostly mobile cards are affected)
> - The output of: apt-cache policy libmutter-6-0
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Luka Maljic (lmalj) wrote : | #189 |
GeForce RTX 2060 Mobile
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
100 /var/lib/
3.
500 http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitaly Sulimov (vsulimov) wrote : | #190 |
Still doesn't work for me after all updates :(
GPU: GeForce MX 250
Command output:
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
100 /var/lib/
3.
500 http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
obobo (ben-autonomic) wrote : | #191 |
Error still present after update for me.
Two 3840x2160 screens - one a DELL XPS 15 laptop screen which is half
the physical size of my BenQ monitor.
Using NVIDIA driver metapackage 440.
With fractional scaling, if I set the inbuilt monitor to 150%, the
EXTERNAL monitor seems to half its visible resolution, quadrupling its
virtual screen size, so only the top left corner is actually displayed
on the monitor.
On 16.05.20 15:55, Ananya Nayan Borah wrote:
> I am facing the same problem.
>
> Nvidia Geforce 940MX/Driver Version: 440.64 .
>
> I tried xrandr scaling but it just throws part of the desktop out of
> the screen. I have a setup of 2 monitors one with 1920x1080 and one with
> 1366x768. It would be great if we can have fractional scaling seperately
> for seperate monitors because on my laptop its really small and its huge
> on the monitor. I tried the workaround provided by @Kristo it works to
> an extent but doesn't really solve everything; still its better to have
> something than nothing. I am new to ubuntu, could someone help me if
> there is any way to manipulate icon size seperately for different
> monitors?
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
rland jon (rlandj) wrote : | #192 |
- journalctl.zip Edit (123.0 KiB, application/zip)
Still doesn't work for me after all updates,and there are side effects... Now every time I boot up, the Desktop's font is very small, even there is no external monitor...if ALT + F2 -> R, then restore :(
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
100 /var/lib/
3.
500 http://
+------
| NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 |
|------
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|======
| 0 GeForce MX150 Off | 00000000:03:00.0 Off | N/A |
| N/A 55C P0 N/A / N/A | 630MiB / 2002MiB | 7% Default |
+------
journalctl.log => restart,Desktop's font NG
journalctl_r.log=> Alt+F2->r ,Desktop's font OK
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christians (script-vollbio) wrote : | #193 |
Wonderful: "sudo apt full-upgrade" pulled in the nvidia updates and fractional scaling works, thank You very much everybody, this makes working on my 4k monitor so much easier!
One small issue remains: The thumbnails of images and documents on the desktop have wrong aspect ratios in all display scales apart from 100%, they are too wide.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
giacomo benelli (benelgiac) wrote : | #194 |
Having exactly the same issue with a Dell XPS 7590, NVIDIA GeForce GTX 1650 and Ubuntu 20.04.1,kernel 5.4.0-42-generic.
I had to revert to nouveau driver, and it now works correctly.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris McDonough (chrism-plope) wrote : | #195 |
I'm updated fully as of today under 20.04 and have the same issue described in OP with an NVIDIA M2000M in a Thinkpad P50 using the proprietary drivers and 1 1080p monitor (the laptop panel) and 1 4k monitor (Dell external).
#83 indicated that they changed things so that their PRIME settings were "on demand" and that made things work for them, but my external monitor just quits working when I change it to that.
Things work mostly as expected with the nouveau driver, but no scaling really works under the proprietary driver. I would use the nouveau driver but it seems very sluggish under any scaling factor.
That said, my issue isn't really about fractional scaling, FWIW. I want to set the external display at 200% and set the internal one at 100%, a configuration which doesn't require fractional. But doing this produces 200% on both panels reliably (and the percentage values in settings reflect that both are set to 200%) under the proprietary drivers.
So right now I can effectively either choose from these three options: a) use nouveau, make both displays work as I would like, but have a very sluggish UI experience b) use proprietary and have text that's too small to read for my old eyes on the 4K external monitor but have a usable built-in display, or b) use proprietary to get reasonably sized text and icons on the 4K external monitor but accept that the built-in monitor is not very useful because its effective resolution is 960x540.
It seems that some people have gotten the combination of proprietary NVIDIA drivers and scaling to work. I would try this on another system to doublecheck but I don't have a machine handy with NVIDIA graphics different than the one in my system (M2000M).
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris McDonough (chrism-plope) wrote : | #196 |
I should note that when I say "proprietary" above, I mean the nvidia-driver-440 package.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris McDonough (chrism-plope) wrote : | #197 |
Here's the output of `nvidia-smi`, FTR:
+------
| NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: 10.2 |
|------
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|======
| 0 Quadro M2000M Off | 00000000:01:00.0 On | N/A |
| N/A 43C P0 N/A / N/A | 1001MiB / 4043MiB | 0% Default |
+------
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris McDonough (chrism-plope) wrote : | #198 |
And apologies for the multicomment spam but the output of apt-cache policy libmutter-6-0
libmutter-6-0:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
100 /var/lib/
3.
500 http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
obobo (ben-autonomic) wrote : | #199 |
Honestly, the only way to get anything approaching reliable "fractional
scaling" that I've found, is to lower the resolution of the smaller
monitor by a ratio similar to its relative screen size. e.g. in my
case, I have two 4k monitors (one external, one a laptop monitor) where
the laptop monitor is about 1/3 of the physical size of the external
monitor. Dropping the internal monitor's resolution from 3840x2160 to
1920x1080 finally makes everything the same size on both screens -
without any slow down - only it's a bit of a waste of a 4k display :-/
On 11.05.20 21:55, Timo wrote:
> Having the same issue...
> But the tmp fix, posted by kristo on 2020-05-06 works great for me too: Browsers, my IDE (Intellij Idea), Slack, Thunderbird, the terminal, they all scale very well.
> I increased the size of the mouse pointer, the dock icons and the icons in nautilus as well. As Daniel wrote on 2020-05-07 the performance is even better compared with fractional scaling activated.
> But it has some downsides. From my point of view the most annoying one: these settings cannot be configured per display but only globally. @Daniel would it be possible to make the settings, mentioned above per display? It might be a more stable way if the performance issues and bugs, related to xrandr and Xorg in general, might occur again with every new nvidia graphic card model or new driver.
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christians (script-vollbio) wrote : | #200 |
Adding to my comment above I have found another issue: The pull-down menu from Auto-Filter is not accessible to the mouse, as it vanishes instantly. The problem disappears after having switched to multiples of 100%.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
giacomo benelli (benelgiac) wrote : | #201 |
I'm wondering if there are any plans about the date for a fix...? It's been months now. Thanks
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David Smoot (davidsmoot) wrote : | #202 |
I do not wish to sound ungrateful or entitled but this bug is literally the one show stopper that is preventing me from doing more work in Linux. I run a triple monitor setup and per monitor fractional scaling is a non-negotiable must for my work.
Can someone explain the root of the problem?
Is it poor driver support on Linux?
Is it the desktop environment lacks mature support for this feature?
Is it just very technically difficult and nobody has the time to handle all the possible combinations?
Every day I sadly hold the space bar to bring up the boot menu to select Windows Boot Manager.
Where is the limitation that prevents a solution here? What can be done to facilitate a fix?
Thanks,
David
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Brian Neltner (neltnerb) wrote : | #203 |
Fundamentally it's fair to blame nvidia's closed source drivers because the open source one seems to do fractional scaling properly.
Other than that what's the point in assigning blame? I'm not sure someone is even paying attention to this bug report, I probably would turn off notifications if it were me volunteering and trying to repair a closed source blob going constantly hassled about not fixing it yet. We really need to learn to be patient.
Maybe we can pitch in to pay someone to make the feature work. Until then...
-------- Original Message --------
On Sep 7, 2020, 5:09 PM, David Smoot wrote:
> I do not wish to sound ungrateful or entitled but this bug is literally
> the one show stopper that is preventing me from doing more work in
> Linux. I run a triple monitor setup and per monitor fractional scaling
> is a non-negotiable must for my work.
>
> Can someone explain the root of the problem?
>
> Is it poor driver support on Linux?
>
> Is it the desktop environment lacks mature support for this feature?
>
> Is it just very technically difficult and nobody has the time to handle
> all the possible combinations?
>
> Every day I sadly hold the space bar to bring up the boot menu to select
> Windows Boot Manager.
>
> Where is the limitation that prevents a solution here? What can be done
> to facilitate a fix?
>
> Thanks,
> David
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> To manage notifications about this bug go to:
> https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Oleg "Nightwing" Lomakin (nightwing666) wrote : | #204 |
Fractional scaling on intel don't work well too(it causes tearing, lags, etc). And it works good only with wayland.
David, you can try #53 workaround(activate drm modeset for nvidia driver). It disabled by default, may be this is root of this problem?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David Smoot (davidsmoot) wrote : | #205 |
@Brian Neltner
The point of my question is to plan.... I don't care about shame, I just care if I should donate to a developer, wait another day, petition Nvidia, or wipe the linux partition because it is pointless.
I am certainly willing to be patient, just looking to somehow quantify the difference between patience and hopelessness and maybe figure out how to help move the ball forward.
David
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
giacomo benelli (benelgiac) wrote : | #206 |
@Brian Neltner
Assigning blame of course is not helping. However, let me mention that some of us in this bug report is running "Ubuntu certified" hardware (i.e. Dell XPS). If that is supposed to mean anything at all, at some point I'd expect at least a plan, as David Smoot was mentioning.
But again, not complaining... Nvidia is free to not fix this at all. Chipping in for devs sounds like a good idea, count me in :)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Felix Raynaud (napafaitlix) wrote : | #208 |
Just a small contribution from my side: the bug is not fixed despite all the latest updates. I'm having a Quadro K5200 with proprietary drivers v440.100 on Ubuntu 20.04 and both fractional scaling (on one monitor) and normal/fractional scaling on multiple monitors with different scaling are broken.
I tried with the latest driver from the ppa:graphics-
No luck with all 3 ways to set the scaling: Gnome control center, xrandr or nvidia-settings. I cannot contribute to the fix itself, but if more details on my configuration is needed, feel free to ask.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
David Smoot (davidsmoot) wrote : | #209 |
I tried the PPA suggested in post 122 (https:/
I'm running Pop OS 20.04 and the displays control panel does not even have fractional scaling buttons to try. I just have choices for "100% 200% 300% 400%" So it is possible the fix from 122 might work if I had the GUI options to try.
Apparently out of sheer coincidence, my updates showed a new "Nvidia 450" driver available. Applied the update and rebooted but I still do not see a settings option for fractional scaling.
I know this is not a Pop OS support ticket but is anyone aware of another mechanism to attempt fractional scaling? I am going to ask the same on Pop OS support.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #210 |
@ David
I think pop-os disabled fractional scaling patch, so get in contact with them please:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
mastorak (mastorak) wrote : | #211 |
@3v1n0
PopOS announced today that they fixed the fractional scaling and that it works with NVIDIA. Maybe you can commnunicate with them as it seems promising.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marco Trevisan (Treviño) (3v1n0) wrote : | #212 |
@mastorak:
Unfortunately they've only packaged the fixes coming from ubuntu: https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
cica-kutya (cica-kutya) wrote : | #213 |
Any information about fixing this bug, please? So many people are affected and still there's no resolution :(
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Oleg "Nightwing" Lomakin (nightwing666) wrote : | #214 |
@cica-kutya there is solution - nvidia kms. And fractional scaling work without any issues(like tearing on intel) for me. I have single gpu setup(no hybrid graphics).
You can activate it by:
1. Set nvidia_drm module option:
$ cat /etc/modprobe.
options nvidia_drm modeset=1
2. Add same option to kernel cmdline:
$ cat /etc/default/grub
....
GRUB_CMDLINE_
....
3. Update initrd
$ sudo update-initramfs -u -k all
4. Reboot
5. Check it
$ sudo cat /sys/module/
Y
6. Activate fraction scaling
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitaly Sulimov (vsulimov) wrote : | #215 |
@nightwing666 Thank you so much! I was fighting with this bug since april and nothing helps, but yours solution is worked perfectly for me!
Running Ubuntu 20.04 on MateBook X Pro, hybrid graphics (Intel + Nvidia GeForce MX250)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mariano Ruiz (marianoruiz) wrote : | #216 |
As @vsulimov mention, the solution from @nightwing666 works, in my case in a ThinkPad X1 Gen 2, but the video scaling in full screen doesn't, it makes any video you try to reproduce in full screen to blink, and if you set the video again in not fullscreen mode the video is scaled x2, or it makes the video player to crash. I tried with the default video player from Ubuntu, with VLC Player and even with Firefox reproducing a video from Youtube, in all the cases the result is the same: the video is reproduced well as long you don't enable full screen video reproduction. I tried with scalling at 125% and 150% and it failed in both cases.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Mariano Ruiz (marianoruiz) wrote : | #217 |
I have to rectify a little bit my affirmation above, everything I said about the video issues is right, but the problem with the video lagging and blinking and re-scalling specially when you move the cursor while watching in full screen mode look like a GNOME problem, not a NVIDIA proprietary driver problem, because after setting up the Nouveau open source driver again, the same problem happens when watching video in full screen, so better to setup the Nvidia driver with the workaround than use the open source drive that does not enable all the acceleration features your video hardware has.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
UV (uvwild) wrote : | #218 |
- monitors.xml Edit (2.5 KiB, application/xml)
i can observe no fractional scaling on a default installation dell xps5790 even with a single monitor (4k). similar connecting a second monitor is not working separately either.
I tried different display resolution to no avail.
I eventually started changing the display resolution and gave up on fractional scaling.
nvidia 450
libmutter-6-0:
Installed: 3.36.6-
--------
xrandr program version 1.5.0
Server reports RandR version 1.6
------------
lspci
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) (rev 02) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: Dell UHD Graphics 630 (Mobile)
Flags: bus master, fast devsel, latency 0, IRQ 176
Memory at eb000000 (64-bit, non-prefetchable) [size=16M]
Memory at 80000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
I found the prime-select toggle and set it to intel...
same issue
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Carlos Pita (carlosjosepita) wrote : | #219 |
@3v1n0
Running PopOS 20.10 right from the installer gets fractional scaling working fine (installed nvidia driver version is 455).
What is it that you said they already packaged? Is this supposed to be fixed in Groovy?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Diego Lineros (diegolineros) wrote : | #220 |
Scaling is working in my Quadro now, but I can't use as I am finding serious performance issues. Not good.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Simon Ryu (neocoin) wrote : | #221 |
>This effects me also:
>
>ubuntu 20.04
>GeForce GTX 1050 Ti Mobile
>4k monitor - usb-c port
>
>That work find in ubuntu 19.10 and same driver.
Above my problem is solved with grub setting.
nvidia_
Thanks everyone!!
Now I'm using Ubuntu 20.10.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
cica-kutya (cica-kutya) wrote : | #222 |
@nightwing666:
Thank you so much for this! It worked!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ramon (rapega12) wrote : | #223 |
@nightwing666:
It worked for me too, thank you!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
giacomo benelli (benelgiac) wrote : | #224 |
I'd like if possible to ask a question to those who report that the nvidia
kms workaround "works".
In my experience, it makes indeed possible to work with fractional scaling,
but the performance is absolutely abysmal: I have tearing issues, drawing
issues and general extreme low performance, comparable to the Xorg driver.
Despite this being OK while waiting for proper support, I don't think this
can be a definitive solution.
So, is it just me doing something wrong and possibly needing to fix
something else or is this the same experience for everybody?
No polemic intent, just would like to assess what "it works" means in this
context.
Thank you very much
On Sun, Dec 13, 2020 at 3:50 PM Ramon <email address hidden> wrote:
> @nightwing666:
> It worked for me too, thank you!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> Status in gnome-control-
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Procedure used:
> 1.
> Fully updated system via apt update && apt upgrade
>
> 2.
> Select the screen setup in gnome control center
>
> 3.
> Click the "Fractional scaling" toggle
>
> 4.
> Select 125% and click the green "use" button top right (it says "Anvend"
> in dansih)
>
> 5.
> Observe that the window has grown a lot, click the "use new settings"
> button
>
> 6.
> The window tells me, I am at 200% scaling. The "200%" option is now
> highlighted.
>
> 7.
> Switch back to 100% and file this bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubuntu-
> ProcVersionSign
> Uname: Linux 5.4.0-21-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 4 09:42:34 2020
> InstallationDate: Installed on 2018-01-14 (810 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
> PackageArchitec
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_
> LANG=da_DK.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-
> Symptom: release-upgrade
> UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
eevo (lucas-e-gray) wrote : | #225 |
kms doesn't work for me, it scales the entire resolution to 125% so much of the screen just falls off of my display to the right and bottom.
My setup is an asus rog g14 hooked up (via hdmi) to a 4k monitor. With the intel hardware fractional scaling works perfectly, so for most things I can simply run using the nvidia hybrid mode and launch applications using dedicated graphics card when I need to. However, blender specifically can still be quite slow in this mode and much faster in nvidia performance mode, but hardly usable since the text in the app is so small.
Really hoping for a solution here! I'm almost always plugged into a desktop setup with this laptop so I'd much rather just run performance mode when working on anything serious.
More info - Ubuntu 20.10, RTX 2060, I've tried nvidia drivers 450 and 455.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Leslie Li (smiledra) wrote : | #226 |
This also affects me. Just thought I'd put a comment in the hope that this will be fixed soon. Fingers crossed!
Changed in mutter (Ubuntu): | |
assignee: | Daniel van Vugt (vanvugt) → nobody |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Diego Lineros (diegolineros) wrote : | #227 |
So... Is that it?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bennett Kanuka (bkanuka) wrote : | #228 |
@benelgiac:
Perfomance for me with modeset=1 is excellent. No tearing or otherwise. Note: I am using the nvidia 460 drivers. I have not tested on older 450/455.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Djerk Geurts (djerkg) wrote : | #229 |
I've got a K1100 and so am on older drivers 390 and modeset makes no difference. When I last tried newer drivers Optimus and/or CUDA broke. So now I'm left with performance mode only and no fractional scaling. Anybody dealt with the same nvidia chip?
tags: | removed: dist-upgrade |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lucas Lamonds (lucas993) wrote : | #230 |
Updated to the 460 drivers and it works with modeset=1. With modeset=1 and 450, it wasn't working.
I have a Quadro K2000 and a 2080 Super dual gpu, single monitor setup.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Leon White (strophy) wrote : | #231 |
I think I am having a related problem, Ubuntu 20.10 with all updates installed, nvidia-
Lenovo W540 i7-4810MQ
Nvidia K2100M + Intel HD 4600
Built-in display 2880x1620 native
External display 1920x1080 native
I want to set 200% scaling on the built-in display and 100% on the external display, but this is not possible. I can set 100% or 200% for both displays:
- 100%: external display looks fine, built-in display too small
- 200%: built-in display looks fine, external display too large
If I enable fractional scaling then I can set different scaling for each display. The size of everything now looks good on both displays, but every second pixel on the external display looks blurry at 100%. This is particularly noticeable when moving the I-bar cursor of the mouse horizontally over text. This is not the case when fractional scaling is not enabled, so I think it is rendering the external display at double the resolution and scaling down with an inappropriate algorithm. How can I set different scaling on different displays without enabling fractional scaling? I wasn't able to try nightwing666's solution because /etc/modprobe.
It's a relatively old GPU and the nvidia site claims 340 is the right driver to use, but Ubuntu offered drivers up to 418 so I am using that. I don't mind using the intel GPU, some other driver or figuring out GPU switching, I just want it to work. Really appreciate any help, thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
yin rong (yr0319) wrote : | #232 |
I'm using fractional scaling in System Settings -> Displays, select 100% for a 2k*1k monitor and 200% scaling a 4k*2k monitor, and then mouse clicked in the wrong position on the first monitor.
wrong position means: mouse click 100,100 and 50,50 got clicked
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Cas (calumlind) wrote : | #233 |
I installed driver version 460.39 and encountered what I assume is the same bug, the only usable scaling was 100% and 200% with the other fractional scaling options 'zoomed' in slightly so the right-hand side of the desktop was cut-off.
I did however find a workaround on AU https:/
Open nvidia settings with root privileges:
sudo nvidia-settings
In PRIME profiles change *Performance* to *On-Demand*
Restart system
Verify that fractional scaling is working again
Reopen nvidia-settings as above and change *On-Demand* back to *Performance*
Restart system
Verify that fractional scaling is still working
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ticket Fabricket (fabricket) wrote : | #234 |
I do confirm the same problem of getting 200% scaling instead of 125% (or any other else) in a Dell XPS 15 9560 laptop with GeForce GTX 1050 Mobile and nvidia-driver-460 (propietary, tested) with an Ubuntu 20.04 LTS just installed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bradley Pearce (blitmaps) wrote : | #235 |
This issue does not affect me on 21.04 with a clean install.
GeForce GTX 1060
460 tested driver
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Geoff Alexander (gdlxn) wrote : | #236 |
I'm seeing the same symptoms, screen scaling 125% gives 200%, when accessing a Ubuntu 20.04 VMware system via xdrp from Windows 10. My graphics driver is
root@geoff-
*-display
description: VGA compatible controller
product: SVGA II Adapter
vendor: VMware
physical id: f
bus info: pci@0000:00:0f.0
version: 00
width: 32 bits
clock: 33MHz
resources: irq:16 ioport:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
yin rong (yr0319) wrote : | #237 |
same bug for me:
ubuntu 21.04
nvidia driver 470
blacklisted nouveau
fractional scale = 125%
desktop is 200% scale, and right and bottom part of desktop is out of monitor.
-------
ubuntu 21.10 have more bug with nvidia driver, so I have to use ubuntu 21.04
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
George Salukvadze (giosal90) wrote : | #238 |
In my case it's even worse: when I set scaling to 100%, it still says 100% and this option is selected, but the real scaling is around 200%
ubuntu 23.04
nvidia-driver 525
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
obobo (ben-autonomic) wrote : | #239 |
"SOLVED" : Move to Wayland on Kbuntu.
On 05.05.23 14:40, George Salukvadze wrote:
> In my case it's even worse: when I set scaling to 100%, it still says 100% and this option is selected, but the real scaling is around 200%
> ubuntu 23.04
> nvidia-driver 525
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christians (script-vollbio) wrote : | #240 |
Solved for me on 23.10 X11 with nvidia-driver-535.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Erkin Alp Güney (erkinalp9035) wrote : | #241 |
possible duplicate of https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
MIKHAIL DYOMIN (dyomin-m) wrote : | #242 |
faced the same bug. Fixed by selecting `NVIDIA (Performance Mode)` profile in NVIDIA X-server settings
Funny - I wrote "gnome- control- center" as the package, once on the web page.