Bug 1516404

Summary: mutter does not remember saved multi monitor configuration
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Pelka <tpelka>
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.5CC: briang, jkoten, nobody+bgollahe, tpelka, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: mutter-3.26.2-6.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1512448 Environment:
Last Closed: 2018-04-10 13:07:25 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:
Bug Depends On: 1512448    
Bug Blocks: 1481395    
Description Flags
modetest when I configured and save my monitor setup
modetest when I re-dock none

Description Tomas Pelka 2017-11-22 14:51:49 UTC
Description of problem:
mutter can't save display layout configuration when fractional scaling is enabled and not only when scaling is enabled

My particular config:
1x full HD monitor
1x QHD monitor with fractional scaling 125%
laptop lid closed, build in display off

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

How reproducible:

Steps to Reproduce:

Actual results:
(gnome-control-center:8374): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent

Expected results:

Additional info:
I started to file this bz in rhbz1512448 so maybe look there for more initial info.

Comment 1 Tomas Pelka 2017-11-22 15:25:53 UTC
Created attachment 1357604 [details]
modetest when I configured and save my monitor setup

Comment 2 Tomas Pelka 2017-11-22 16:29:21 UTC
Created attachment 1357668 [details]
modetest when I re-dock

Comment 11 errata-xmlrpc 2018-04-10 13:07:25 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.