Nvidia gnome control center scale gets overridden on reboot

Bug #1720838 reported by Thomas Cross
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mutter
Expired
Medium
mutter (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session.
If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%".

To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.82 Wed Jul 19 21:16:49 PDT 2017
 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
BootLog:

CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 2 11:34:59 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
 nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230]
InstallationDate: Installed on 2017-10-02 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: LENOVO 20ENCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET70W (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ENCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20ENCTO1WW
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 2 11:32:23 2017
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.3-1ubuntu6

Revision history for this message
Thomas Cross (chmoder) wrote :
Thomas Cross (chmoder)
description: updated
Revision history for this message
In , Thomas Cross (chmoder) wrote :

Created attachment 360874
screenshot of where I go to keep setting the scale

Operating System:
  Ubuntu 17.10 Beta 2

How to reproduce:
  When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session.
  If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%".
  I don't think this happens till I install the Nvidia driver by performing:
ubuntu-drivers devices
sudo apt-get install nvidia-xxx

Work Around:
  To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time.

Logs, settings, screenshots, more details, etc:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720838

Revision history for this message
In , Andre Klapper (a9016009) wrote :

Thanks for reporting this.
Which mutter version is this about? Setting the "Version" field is welcome.

Revision history for this message
In , Thomas Cross (chmoder) wrote :

Hi Andre,

Thanks for asking. Please continue to let me know how I can help.

tcross@karen:~$ mutter --version
mutter 3.26.0
Copyright © 2001-2011 Havoc Pennington, Red Hat, Inc., and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

affects: xorg (Ubuntu) → mutter (Ubuntu)
Changed in mutter:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in mutter (Ubuntu):
status: New → Incomplete
Changed in mutter:
importance: Medium → Unknown
status: Confirmed → Unknown
Changed in mutter (Ubuntu):
status: Incomplete → Won't Fix
Changed in mutter:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Gnome-sysadmin (gnome-sysadmin) wrote :

GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.

Changed in mutter:
status: Confirmed → Expired
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.