Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
.*Mutter* now allows for mass-deployable homogenized display configuration
The *Mutter* window manager now makes it possible to deploy pre-set display configurations for all users on a system. As a result, *Mutter* no longer requires that the configuration for each user is copied to its own configuration directory, but it can use a system wide configuration file instead. This feature makes *Mutter* suitable for mass deployment of homogenized display configuration.
To set the configuration for a single user, create and populate the `~/.config/monitors.xml` file. For the login screen in particular, use the `~/gdm/.config/monitors.xml` file. For system-wide configurations, use the `/etc/xdg/monitors.xml` file.
Description of problem:
- As things currently stand, mutter and/or ~/.config/monitors.xml overrides xorg/xorg.conf, and cannot use a generic configuration. It flatly requires that the configuration be defined using display serial numbers (in current versions, including in Fedora 28). This creates a major problem for mass deployment where it is not feasible to know display serial numbers. Additionally, the configuration used to be read from /etc/gnome-settings-daemon/monitors.xml but that seems to have been dropped. This change would need to be reverted in addition to a method to allow "generic" non-serialized display configurations for the purpose of mass-deployment/automation/homogenization
How would the customer like to achieve this? (List the functional requirements here)
- A generic display configuration can be passed via kickstart post-install script/ansible/some other deployment automation solution that sets the default display configuration
Is there already an existing RFE upstream or in Red Hat Bugzilla?
- No
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
- As soon as possible
Is the sales team involved in this request and do they have any additional input?
- No
List any affected packages or components.
- mutter
- gnome-settings-daemon
- control-center
Would the customer be able to assist in testing this functionality if implemented?
- Yes
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/RHBA-2019:2044