Ubuntu
gnome-control-center package

gnome-control-centre fails to change display resolution due to "Scale 2 not valid for resolution"

Bug #1716322 reported by Rocko
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

When I run g-c-c and try to change the laptop's display resolution from 4K to 1920x1080, it fails silently (it should really show the error, but that's another bug). If I have run it from the console, this message appears:

(gnome-control-center:5356): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Scale 2 not valid for resolution 1920x1080

I'm currently running in an X11 sesssion, but that's only because Wayland keeps crashing and the session seems to be defaulting back to X11 when I run it again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.25.92.1-0ubuntu1
Uname: Linux 4.13.1-041301-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 13:57:59 2017
InstallationDate: Installed on 2017-08-16 (25 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-08-17 (25 days ago)

Revision history for this message
Rocko (rockorequin) wrote :
Revision history for this message
Rocko (rockorequin) wrote :

This might be related to the setting "org.gnome.desktop.interface scaling-factor", because if I manually set it to zero (gsettings set org.gnome.desktop.interface scaling-factor 0), g-c-c now can change the display resolution.

But g-c-c should not fail just because of an invalid setting.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Dana Goyette (danagoyette) wrote :

Same for me: I can use xrandr manually in an Xorg session, but not in the Wayland sesson.

From some stuff I read online, it seems like Gnome is trying to prevent you from making the virtual resolution too low, but if it's already too low, now you're stuck like that, and it really ought to be up to the user.

I hardly think 2x is too much for an 8 inch 1200x1920 (boots in portrait, yay!) monitor.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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