[nvidia] Screen scaling 125% gives 200%

[PerJensen]

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-release-upgrader-core 1:20.04.16
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
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)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

[PerJensen (per-net-es)]

Funny - I wrote "gnome-control-center" as the package, once on the web page.

[PerJensen (per-net-es)]

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

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you add your 'journalctl -b 0' log after getting the issue?

[Daniel van Vugt (vanvugt)]

The bug might still be gnome-control-center, gnome-shell or mutter.

[PerJensen (per-net-es)]

Here is the journalcl -b 0 output, when scaling from 100% to 200% and back to 100%

[PerJensen (per-net-es)]

Oops.

The first journalctl is not the for testcast.

This is the log when I select 125 % scaling and get 200%

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marco Trevisan (Treviño) (3v1n0)]

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/gnome-shell

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

[Pål Andreassen (paal-andreassen)]

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.

[PerJensen (per-net-es)]

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

[PerJensen (per-net-es)]

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

[Sebastien Bacher (seb128)]

Could you also try outside of GNOME using xubuntu or another desktop to rule out shell interfering?

[PerJensen (per-net-es)]

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

[Daniel van Vugt (vanvugt)]

See also bug 1873403.

[ThOR27 (thor27-gmail)]

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

[Daniel van Vugt (vanvugt)]

I wonder if the nvidia driver doesn't support the same version/featureset of Xrandr as the modeset driver?...

https://www.x.org/releases/X11R7.7/doc/randrproto/randrproto.txt

[Pål Andreassen (paal-andreassen)]

$ xrandr --version
xrandr program version 1.5.0
Server reports RandR version 1.6

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jesus (salseandotv)]

I also have the same problem, regards.

[Vitaly Sulimov (vsulimov)]

Same for me.
Ubuntu 20.04 nvidia-driver-440, GeForce MX250.

[Greg Cavazos (drayak335)]

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"

[Dong Xuan Huy (huydx.evil)]

I have exactly the same bug.
Ubuntu 20.04, GeForce GT 730M, using nvidia-driver-440

[ilovebytes (ilovebytes)]

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 :(

[kitezila (kitezila)]

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

[Bradley Pearce (blitmaps)]

This effects me also:

GeForce GTX 1060

440 tested driver

[Konstantin (soulkeeper)]

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
             0.000000 1.000000 0.000000
             0.000000 0.000000 1.000000
            filter:
 _MUTTER_PRESENTATION_OUTPUT: 0
 CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
 EDID:
  00ffffffffffff0026cd3766db0b0000
  301d0104b53c2278fb0c95ab554ca024
  0d50542108009500a9c0a940b300d1c0
  d1cae1008180565e00a0a0a029503020
  350055502100001a000000ff00313135
  32313934383033303335000000fd0030
  4678781e010a202020202020000000fc
  00504c32373932510a202020202001c6
  020318f14b100504030201111213141f
  23090707830100004c6b0050a0a03050
  0820280855502100001a000000000000
  00000000000000000000000000000000
  00000000000000000000000000000000
  00000000000000000000000000000000
  00000000000000000000000000000000
  00000000000000000000000000000062
 BorderDimensions: 4
  supported: 4
 Border: 0 0 0 0
  range: (0, 65535)
 SignalFormat: DisplayPort
  supported: DisplayPort
 ConnectorType: DisplayPort
 ConnectorNumber: 2
 _ConnectorLocation: 2
 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...

[Fusion (bornolbers)]

This effects me also:

ubuntu 20.04

GeForce GTX 1050 Ti

440 tested driver

4k monitor - displayport

[smallcham (smallcham)]

This effects me also:

ubuntu 20.04

GeForce GTX 1660

4k monitor - displayport

I tryed '440 tested'、'435'、'nouveau' driver and i also tryed 'NVIDIA official driver 440.82', all of then has this problem.

[eTushar89 (etushar89)]

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 |
+-------------------------------+----------------------+----------------------+

[Fusion (bornolbers)]

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

[David Smoot (davidsmoot)]

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

[Brian Neltner (neltnerb)]

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://bugs.launchpad.net/bugs/1870736
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions

[Oleg "Nightwing" Lomakin (nightwing666)]

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?

[David Smoot (davidsmoot)]

@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

[giacomo benelli (benelgiac)]

@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 :)

[Felix Raynaud (napafaitlix)]

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-drivers/ppa repository, no help there. I confirm that scaling is working with the nouveau driver, but this is not a solution for me since I need features like CUDA, opencl or compatibility with VMWare 3D acceleration.

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.

[David Smoot (davidsmoot)]

I tried the PPA suggested in post 122 (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/comments/122) last night. No luck

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.

[Marco Trevisan (Treviño) (3v1n0)]

@ David

I think pop-os disabled fractional scaling patch, so get in contact with them please:
 https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c

[mastorak (mastorak)]

@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.

[Marco Trevisan (Treviño) (3v1n0)]

@mastorak:

Unfortunately they've only packaged the fixes coming from ubuntu: https://github.com/pop-os/mutter/commits/master_focal

[cica-kutya (cica-kutya)]

Any information about fixing this bug, please? So many people are affected and still there's no resolution :(

[Oleg "Nightwing" Lomakin (nightwing666)]

@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.d/nvidia-modeset.conf
options nvidia_drm modeset=1
2. Add same option to kernel cmdline:
$ cat /etc/default/grub
....
GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1 quiet splash"
....
3. Update initrd
$ sudo update-initramfs -u -k all
4. Reboot
5. Check it
$ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
6. Activate fraction scaling

[Vitaly Sulimov (vsulimov)]

@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)

[Mariano Ruiz (marianoruiz)]

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.

[Mariano Ruiz (marianoruiz)]

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.

[UV (uvwild)]

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-1ubuntu0.20.04.2
--------
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

[Carlos Pita (carlosjosepita)]

@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?

[Diego Lineros (diegolineros)]

Scaling is working in my Quadro now, but I can't use as I am finding serious performance issues. Not good.

[Simon Ryu (neocoin)]

>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_drm.modeset=1

Thanks everyone!!

Now I'm using Ubuntu 20.10.

[cica-kutya (cica-kutya)]

@nightwing666:
Thank you so much for this! It worked!

[Ramon (rapega12)]

@nightwing666:
It worked for me too, thank you!

[giacomo benelli (benelgiac)]

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://bugs.launchpad.net/bugs/1870736
>
> Title:
> [nvidia] Screen scaling 125% gives 200%
>
> Status in gnome-control-center package in Ubuntu:
> 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-release-upgrader-core 1:20.04.16
> ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
> Uname: Linux 5.4.0-21-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> 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)
> PackageArchitecture: all
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=da_DK.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-release-upgrader
> Symptom: release-upgrade
> UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions
>

[eevo (lucas-e-gray)]

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.

[Leslie Li (smiledra)]

This also affects me. Just thought I'd put a comment in the hope that this will be fixed soon. Fingers crossed!

[Diego Lineros (diegolineros)]

So... Is that it?

[Bennett Kanuka (bkanuka)]

@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.

[Djerk Geurts (djerkg)]

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?

[Lucas Lamonds (lucas993)]

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.

[Leon White (strophy)]

I think I am having a related problem, Ubuntu 20.10 with all updates installed, nvidia-driver-418-server driver.

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.d/nvidia-modeset.conf does not exist for me, but `sudo cat /sys/module/nvidia_drm/parameters/modeset` returns Y so I think it is enabled anyway.

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!

[yin rong (yr0319)]

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

[Cas (calumlind)]

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://askubuntu.com/a/1321851/8570 that might help identify the problem.

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

[Ticket Fabricket (fabricket)]

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.

[Bradley Pearce (blitmaps)]

This issue does not affect me on 21.04 with a clean install.

GeForce GTX 1060

460 tested driver

[Geoff Alexander (gdlxn)]

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-ubuntu-2004:~# lshw -c video
  *-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
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=vmwgfx latency=64
       resources: irq:16 ioport:1070(size=16) memory:e8000000-efffffff memory:fe000000-fe7fffff memory:c0000-dffff

[yin rong (yr0319)]

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

[George Salukvadze (giosal90)]

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

[obobo (ben-autonomic)]

"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
>

[Christians (script-vollbio)]

Solved for me on 23.10 X11 with nvidia-driver-535.

[Erkin Alp Güney (erkinalp9035)]

possible duplicate of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285 ?