GNOME Bugzilla – Bug 709062
GDM does not display login screen on external monitor even when booted with the laptop lid closed.
Last modified: 2018-05-24 10:57:20 UTC
This has been an issue for a while now. I searched several times for duplicate bug report but only came up with one that was submitted back on v3.4 (688413). If I boot my laptop with the lid closed, which is my primary setup, GDM displays the login fields on the laptop screen and only gray wallpaper and top bar on my external monitor. I can press enter, input password, press enter again to login and then GDM immediately displays Shell on my external monitor and shuts off the laptop screen as configured. I understand why GDM isn't reading the monitor.xml until login as it is specific to the user but there should be a global configuration for this as well. The workaround that I have been using is to copy my monitors.xml file to ~gdm/.config.
I have a similar problem where I have my TV connected as a secondary monitor, and even though the TV is off, gdm decides to put the greeter dare.
(In reply to comment #1) > I have a similar problem where I have my TV connected as a secondary monitor, > and even though the TV is off, gdm decides to put the greeter dare. Have you tried the workaround I mentioned? Setup your display while logged in using GNOME settings and then copy the setup over to gdm like this: cp /home/user/.config/monitors.xml ~gdm/.config
This downstream report could be the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=1101879
This bug could be related? https://bugzilla.gnome.org/show_bug.cgi?id=748098
> Have you tried the workaround I mentioned? Setup your display while logged > in using GNOME settings and then copy the setup over to gdm like this: > > cp /home/user/.config/monitors.xml ~gdm/.config Works for me on Debian Stretch. cp /home/user/.config/monitors.xml /var/lib/gdm3/.config chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/monitors.xml chmod 644 /var/lib/gdm3/.config/monitors.xml
-- 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/168.