Bug 1567040

Summary:	GNOME Tweak Tool still enables user to select scaling factor
Product:	Red Hat Enterprise Linux 7	Reporter:	Jonas Ådahl <jadahl>
Component:	gnome-tweak-tool	Assignee:	Carlos Soriano <csoriano>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.5	CC:	alanm, jkoten, klember, ptalbert, tpelka
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1567224 (view as bug list)		Environment:
Last Closed:	2018-10-30 10:21:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1567224

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 2 Kalev Lember 2018-04-13 12:28:44 UTC

http://pkgs.devel.redhat.com/cgit/rpms/gnome-tweak-tool/commit/?h=rhel-7.6&id=a18de1f6a2e39ee5021e2e7efd23edc76678a30f

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