[nvidia] Screens turn off when setting display scaling to 200%

Bug #1869750 reported by Adam Grubbs
88
This bug affects 22 people
Affects Status Importance Assigned to Milestone
Mutter
Fix Released
Unknown
mutter (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Issue: When setting display scaling to 200% in GNOME settings with proprietary nvidia drivers installed displays go to sleep until settings automatically revert to previous settings.

Steps to reproduce:

- Install proprietary nvidia drivers

- Open GNOME settings

- Navigate to Display settings

- Set display scaling to 200%

NOTE: This issue has been solved in upstream mutter git master branch. Confirmed on both Arch and Fedora packages that have been created from mutter master branch.

GPU: GeForce GTX 1080 Ti
Driver: 440.64

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 11:01:56 2020
InstallationDate: Installed on 2020-03-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Adam Grubbs (adam-ryan-grubbs) wrote :
Revision history for this message
Adam Grubbs (adam-ryan-grubbs) wrote :
Changed in mutter (Ubuntu):
status: New → Fix Committed
tags: added: fixed-in-3.36.1 fixed-upstream
summary: - Screens turn off when setting display scaling to 200%
+ [nvidia] Screens turn off when setting display scaling to 200%
tags: added: nvidia
Changed in mutter (Ubuntu):
importance: Undecided → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

With the bug:

$ xrandr
Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary (normal left inverted right x axis y axis)
   1920x1200 59.95 + 59.88

Without the bug:

$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200 59.95*+ 59.88

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

^^^
When the bug is happening my monitor has no position ("+0+0") and no current mode ("*").

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Workaround: Stick to 100% scale. Either edit your ~/.config/monitors.xml or just delete it and reboot.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I am pleased to report that 3.36.1-3ubuntu1~wip2 fixes the problem for me.

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4010

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.36.1-3ubuntu1

---------------
mutter (3.36.1-3ubuntu1) focal; urgency=medium

  * Merge with debian, with new upstream releases and cherry-picked fixes:
    - Screens turn off when setting display scaling to 200% (LP: #1869750)
    - Use hardware cursor for DisplayLink devices (LP: #1867757)
    - Fix popup menus with using focus-follow-mouse (LP: #1871107)
    - Window manager key events are sent to the terminal (LP: #1866094)
    - Ensure assertion 'window->unmanaging || workspace != NULL' (LP: #1864326)
    - Shell crash on meta_wayland_surface_role_get_window (LP: #1869837)
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
    - Refreshed to respect upstream changes
    - Fixed a bug causing windows using direct-rendering to be continuously
      resized, keeping ability to use shell UI (LP: #1862081)
  * Remaining changes with debian:
    - debian/control:
      + Update VCS flags to point to ubuntu salsa branch
    - debian/gbp.conf: update branch to point to ubuntu/master
    - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr

mutter (3.36.1-3) experimental; urgency=medium

  * Team upload
  * Update to upstream gnome-3-36 branch, commit 3.36.1-16-gdb164bcfa
    - Fix a crash during X11 drag-and-drop, for example when dragging
      a JPEG file onto GIMP's splash screen
    - Fix a crash in X11 input device handling
    - Translate coordinates of absolute input devices for rotated screens

mutter (3.36.1-2) experimental; urgency=medium

  * Team upload
  * Standards-Version: 4.5.0 (no changes required)
  * d/copyright: Consolidate entries and update
  * Update to upstream gnome-3-36 branch, commit 3.36.1-13-gbc47f0a1a

mutter (3.36.1-1) experimental; urgency=medium

  * Team upload
  * New upstream release
  * d/copyright: Update
  * Refresh patches
  * Update symbols file.
    Note that this includes ABI breaks: some symbols that are only used
    internally have disappeared from mutter's private fork of Clutter and
    Cogl. The only user of this version of mutter is GNOME Shell, which
    does not use these symbols.
  * d/patches: Update from gnome-3-36 branch up to 3.36.1-8-ge339a57dd
  * d/p/clutter-stage-Don-t-assume-stage-relayouts-reallocate-eve.patch:
    Add patch proposed upstream to fix a gnome-shell crash with the
    "Native window placement" extension.

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 09 Apr 2020 14:40:58 +0200

Changed in mutter (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Michael (mrzxvp5j-ubuntu) wrote :

I can confirm that this issue has been resolved with today's (2020-04-10) update in Focal Fossa.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually the problems continue in bug 1873403.

Changed in mutter:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.