After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748098 - monitors.xml not working in GDM when running under Wayland
monitors.xml not working in GDM when running under Wayland
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
3.22.x
Other Linux
: Normal minor
: ---
Assigned To: GDM maintainers
GDM maintainers
See workaround in comment 7
Depends on: 761678
Blocks:
 
 
Reported: 2015-04-18 10:31 UTC by Mario H
Modified: 2018-05-24 11:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mario H 2015-04-18 10:31:40 UTC
I copied the monitors.xml
from 
~/.config/monitors.xml directory
to
~gdm/.config/monitors.xml

This way of configuring the monitor setup worked until the newest update from the Arch repositories.

Since the newest update GDM seems to ignore the file.
I recreated the file but it doesn't help

Thus my monitor setup is wrong in the login screen. Gnome-shell is working fine.

It's not a big deal. However it's annoying.
Comment 1 Florian Latifi 2015-05-28 21:21:18 UTC
I am also facing this problem.

Using a laptop with a second monitor. On the gdm login screen, the monitors aren't arranged correctly. In gnome-shell both monitors are arranged correctly, because i configured them in the gnome settings. Copied the monitors.xml file into /var/lib/gdm/.config/, but it does not help.
Comment 2 Simo 2015-10-28 10:40:18 UTC
Found a solution that worked for me:

Once you've got your monitors.xml file set up here:
/var/lib/gdm/.config/monitors.xml
a.k.a. ~gmd/.config/monitors.xml

Edit the:
/etc/gdm/custom.conf

and uncomment:
WaylandEnable=false

This worked in Gnome 3.18 on Arch Linux.

Got the solution from here:
https://bbs.archlinux.org/viewtopic.php?id=196219
Comment 3 Jeremy Newton 2016-01-22 01:02:07 UTC
This was reported downstream Fedora as well:

https://bugzilla.redhat.com/show_bug.cgi?id=1184617
Comment 4 Rui Matos 2016-01-28 18:34:14 UTC
This is probably due to the output names being different when mutter is running under X from when it runs natively on the KMS interfaces. If you save a monitors.xml file in a wayland session then it should apply to gdm's wayland (login) session too.

Unsure if this is a bug though since manually copying that file around isn't really intended. Ideally GDM would have a DBus API that g-c-c could use to set the "system wide" display configuration.
Comment 5 Jeremy Newton 2016-02-07 18:14:35 UTC
Fair enough; I made an enhancement request for gnome control center.
Comment 6 Matthias Clasen 2016-03-14 10:26:34 UTC
Did we have any plan for fixing this ?
Comment 7 Florian Latifi 2016-07-12 07:16:13 UTC
Okay so since gdm runs in a wayland session per default, the fix is to log in with a wayland session, set up your monitors within gnome-control-center and then copy the ~/.config/monitors.xml file to /var/lib/gdm/.config/monitors.xml, hope it helps.
Comment 8 Age Bosma (IRC: Forage) 2016-10-18 17:35:01 UTC
The work-around provided by Florian, log in with a wayland session for a wayland monitors.xml, does the trick for me on Ubuntu GNOME 16.10 with GNOME 3.22.

The different in the monitors.xml file is other names for the used two outputs. Where in an X session the outputs are named "DisplayPort-1" and "DisplayPort-2", the same ones are named "DP-2" and "DP-3" in a wayland session.
Comment 9 Daniel van Vugt 2018-01-09 03:09:59 UTC
Duplicate of bug 729652?
Comment 10 GNOME Infrastructure Team 2018-05-24 11:10:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/224.