21
GDM not honoring custom monitor config
(lemmy.ml)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
When you copy over your monitor config, are you correcting the ownership/permissions?
The little scriptlet I made to combat a previous nvidia/wayland multi-monitor headache boils down to:
Maybe double check if GDM is ignoring wayland as well, I've definitely had that happen in the past too.
Just checked the ownership of the monitor config, it was
gdm:root
, so I changed the ownership togdm:gdm
and rebooted. Still facing the same issue.Didn’t see any error messages in the logs about not being able to load wayland, but just to confirm, I ran
loginctl show-session {gdm session id} -p Type
which returnsType=wayland
, so it’s definitely running under wayland. I have an AMD GPU though so I wouldn’t expect there to be any problems there.Not seeing anything else weird in the logs that are jumping out as strange to me either, so a bit at a loss here. Any other suggestions?
Yeah, seems like it should just be working...
You've probably already got this covered, but when you created your user
monitors.xml
config, did you have the dummy plug connected and disabled?Maybe the config:
Yes. Here’s the contents I currently have in
/var/lib/gdm/.config/monitors.xml
:The disabled dummy plug is the “Evanlak8K V2” device while my functional monitor is my Samsung Odyssey OLED G9. This config is the same as the one currently running on my GNOME desktop config, but in GDM still defaults to the enabled dummy plug, even with the fixed ownership.
At this point, do you think I should issue a report on GDM’s repository? Maybe the devs there would have more insight
Does this use any experimental options you enabled in your dconf?
Edit: Kontext: https://gitlab.gnome.org/GNOME/gdm/-/issues/224#note_2271241
My monitors.xml has two
<configuration>
blocks, with the only real difference being that one has<layoutmode>physical</layoutmode>
and the second has<layoutmode>logical</layoutmode>
. I don't really think that'd be the issue here though, because if the dummy plug is listed as disabled it shouldn't be trying to use it anyway...?I think you're right in reporting it to the GDM repo, at a minimum someone there will know where to point you towards figuring this out. Maybe the GNOME Mutter repo might be a related stop for this too, seeing that's the part generating the monitors.xml...
The things that are supposed to be simple are always the bits that suck the most!
Very well said. Thank you very much for your help. I wouldn’t have known to check the ownership issues or if GDM were properly running Wayland were it not for your help. I’ll reach out to the GNOME devs on the relevant repositories and see if they might be able to point me in the right direction. Thank you for your time and expertise.