Bug 2001655
| Summary: | Unable to disable xrandr configuration in wayland, need to be able to set or enforce monitor setup irregardless of users montiors.xml | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | mkielian <mkielian> |
| Component: | mutter | Assignee: | Jonas Ådahl <jadahl> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Kopec <pekopec> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.4 | CC: | aubin.guillemette, fmuellner, jwright, pekopec, sbarcomb, tpelka |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| 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
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 14:26:16 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: | |||
|
Description
mkielian@redhat.com
2021-09-06 16:56:53 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 ? (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. 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. with monitors.xml in /etc/xdg and policy set to system all users used that xml instead of user one 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 |