RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2001655 - Unable to disable xrandr configuration in wayland, need to be able to set or enforce monitor setup irregardless of users montiors.xml
Summary: Unable to disable xrandr configuration in wayland, need to be able to set or ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mutter
Version: 8.4
Hardware: All
OS: All
medium
medium
Target Milestone: rc
: ---
Assignee: Jonas Ådahl
QA Contact: Peter Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-06 16:56 UTC by mkielian@redhat.com
Modified: 2022-05-10 14:52 UTC (History)
6 users (show)

Fixed In Version: mutter-3.32.2-61.el8
Doc Type: Enhancement
Doc Text:
Feature: Configure system level monitor configuration policy Reason: Ability to inhibit overriding system monitor configuration Result: Monitor configuration provided by system will always be used
Clone Of:
Environment:
Last Closed: 2022-05-10 14:26:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME mutter merge_requests 2030 0 None None None 2021-10-01 08:20:32 UTC
Red Hat Issue Tracker RHELPLAN-96350 0 None None None 2021-09-06 17:39:08 UTC
Red Hat Product Errata RHBA-2022:1947 0 None None None 2022-05-10 14:26:21 UTC

Description mkielian@redhat.com 2021-09-06 16:56:53 UTC 
Description of problem:

Under RHEL7 it used to be possible to disable xrandr setup using the following dconf key; 


dconf write /org/gnome/settings-daemon/plugins/xrandr/active false

This would force the system to ignore any user's ~/.conf/monitors.xml file and enforce a local only monitor configuration.  


This is useful with dealing with workstations, especialy stations that utilize either multiple monitors or non-standard mopnitors, etc.




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


This setting was entirely removed from Gnome in 3.26, per engineering:

RHEL 7.5 - 7.9
All of RHEL 8 





How reproducible:


Steps to Reproduce:
1.  Login and add the following dconf key: dconf write /org/gnome/settings-daemon/plugins/xrandr/active false

2. Run: "dconf update"
3. Restart X server/Gnoem or Reboot.

Actual results:

Monitor settings still read ~/.conig/monitors.xml


Expected results:

Monitor should be defaulting to setting setup in: 

/etc/X11/xorg.conf


Additional info:

In RHEL8 this would be after disabling wayland and setting it up to use Xorg server.


Functionality ( to set a local enforced monitor configuration ) should be added to Gnome/Xerver or incorporated into wayland moving forward.
Comment 1 Joe Wright 2021-09-09 17:47:02 UTC 
Ffor one specific type of workstation they want to set a static configuration for all users, regardless of what they have in their ~/.config/monitors.xml. In RHEL7 I could do that by setting the configuration in /etc/X11/xorg.conf and disabling the xrandr plug-in. How can they achieve the same thing in RHEL8 ?
Comment 2 Jonas Ådahl 2021-09-13 15:59:44 UTC 
(In reply to Joe Wright from comment #1)
> Ffor one specific type of workstation they want to set a static
> configuration for all users, regardless of what they have in their
> ~/.config/monitors.xml. In RHEL7 I could do that by setting the
> configuration in /etc/X11/xorg.conf and disabling the xrandr plug-in. How
> can they achieve the same thing in RHEL8 ?

Should this disable the ability to use Settings to create temporary configurations as well? What kind of level of lock-down is needed? E.g. would a setting that in theory can be toggled by the user be adequate or should this be enforced on a system level?

I see the suggestion of reusing a legacy setting from a gnome-settings-daemon; that has all the issues described above.

E.g. an alternative could be writing a system level monitors.xml that tells mutter to not use configuration files in the users home directory.
Comment 3 aubin.guillemette 2021-09-13 16:29:17 UTC 
We are not looking for lock-down...our issue is that home directories are shared by NFS and used on different workstations with different monitor configuration. On some workstation we want to be able to configure the monitors at the system level and not have users' monitors.xml mess it up. If we could have a system-level monitors.xml that takes precedence over the one in the users' home that would work.
Comment 5 Peter Kopec 2022-02-09 19:45:04 UTC 
with monitors.xml in /etc/xdg and policy set to system all users used that xml instead of user one
Comment 8 Peter Kopec 2022-02-15 19:36:10 UTC 
Based on testing in Comment 5 moving to verified.
Comment 10 errata-xmlrpc 2022-05-10 14:26:16 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 (mutter bug fix and enhancement update), 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/RHBA-2022:1947
Note You need to log in before you can comment on or make changes to this bug.