Bug 1567040 - GNOME Tweak Tool still enables user to select scaling factor
Summary: GNOME Tweak Tool still enables user to select scaling factor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-tweak-tool
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Carlos Soriano
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1567224
TreeView+ depends on / blocked
 
Reported: 2018-04-13 10:26 UTC by Jonas Ådahl
Modified: 2018-10-30 10:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1567224 (view as bug list)
Environment:
Last Closed: 2018-10-30 10:21:19 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3140 0 None None None 2018-10-30 10:22:21 UTC

Description Jonas Ådahl 2018-04-13 10:26:07 UTC
Description of problem:

With GNOME 3.26, the management of monitor scaling factors was moved from a global setting (managed either directly via the gsettings entry, or via GNOME Tweak Tool -> Window -> Scaling factor) to the Settings app. Changing this setting the old way is incompatible with how the scaling is managed in GNOME 3.26, so not having rebased GNOME Tweak Tool (which removed the scaling factor tweakability in 3.26) makes it easy to mess HiDPI support up.

Version-Release number of selected component (if applicable):

gnome-tweak-tool-3.22.0-1.el7

Additional info:

Since the tweak tool doesn't allow to "reset" the scaling factor, to get rid of the problem after having tweaked, the user must change back the org.gnome.desktop.interface scaling-factor setting to 0.

Comment 7 errata-xmlrpc 2018-10-30 10:21:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3140


Note You need to log in before you can comment on or make changes to this bug.