From Gentoo Wiki
Jump to:navigation Jump to:search
Other languages:

As part of the GNOME desktop suite, the GNOME Display Manager (GDM) is the daemon responsible for launching graphical display sessions via the Xorg display server or the gnome-shell directly via Wayland display protocol.



To enable debugging, edit the following configuration file:

FILE /etc/gdm/custom.conf
# Uncomment the line below to turn on debugging

On systems running systemd, this will configure GDM to write verbose output to the journal. Be sure to disable debugging when finished resolving any issues to save space in the journal.

See upstream's debug documentation for more details on debugging GDM.


GDM and Optimus

See the GDM section of the NVIDIA Optimus article when using GDM on platforms utilizing NVIDIA Optimus.

Stop GDM from loading SSH Agent

GDM will call the SSH Agent upon login. This automation can cause an issue in several situations.

To disable this behavior, create or modify the user's ~/.pam_environment as indicated below.

FILE ~/.pam_environmentPreventing GDM from loading the SSH Agent
# disable the overwrite of SSH_AUTH_SOCK by gnome-shell
# Load gpg-agent as ssh-agent (optional, use only if you want to use gpg-agent as ssh-agent)
SSH_AUTH_SOCK DEFAULT="${XDG_RUNTIME_DIR}/gnupg/S.gpg-agent.ssh"

Enable tap to click in GDM

Tap to click is disabled by default in GDM's environment. Enabling this feature requires setting GNOME option org.gnome.desktop.peripherals.touchpad tap-to-click for the gdm user.

Grant permissions for gdm to access the X server:

user $xhost +SI:localuser:gdm

Then set the gsettings configuration value as the gdm user to enable tap to click:

user $sudo -u gdm gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true

The new setting will take effect after restarting the GDM service.

GDM crashes when attempting to launch a GNOME Wayland session

Problem: GDM is crashing when attempting to launch a GNOME Wayland session. Known to affect at least gdm-3.32.0.

Cause: This is most likely occurring because the NVIDIA kernel module is being loaded by the kernel and subsequently detected by udev - even if it not being used by the graphics stack. The udev rule (see /lib/udev/rules.d/61-gdm.rules) is shipped with GDM. Even if the system is not actively using the NVIDIA driver or NVIDIA hardware to render graphics, the rule will still trigger the /usr/libexec/gdm-disable-wayland" executable. This writes a configuration file to /run/gdm/custom.conf which is read by GDM at start time and disables support for Wayland sessions.

Solution: There are a few solutions to this problem:

  1. Uninstall the x11-drivers/nvidia-drivers package and remove the installed NVIDIA kernel modules. This is most likely the easiest solution, since it will remove the NVIDIA kernel module that triggers the udev rule (nvidia.ko) and prevent it from returning.
  2. Blacklist the NVIDIA kernel module from loading. This can is performed different ways: kernel command-line parameters via the secondary bootloader (GRUB, systemd-boot, etc.) or adding a blacklist configuration file via modprobe.d.
  3. System administrators that want to keep the NVIDIA binary blob available for other desktop environments, but want to launch GNOME on Wayland and follow this last solution. It is simplest to manually editing the offending part of the udev rule so that gdm-disable-wayland cannot create the custom configuration file. To be safe, review Xorg's configuration files in the /etc/X11 directory to be sure NVIDIA is not being set as the primary Xorg driver. It is also a good idea to review the Xorg.0.log to double check. Simply comment out the last line:
FILE /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Cirrus chipsets
ATTR{vendor}=="0x1013", ATTR{device}=="0x00b8", ATTR{subsystem_vendor}=="0x1af4", ATTR{subsystem_device}=="0x1100", RUN+="/usr/libexec/gdm-disable-wayland"
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/libexec/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
#DRIVER=="nvidia", RUN+="/usr/libexec/gdm-disable-wayland"

GDM produces an all-black screen when more than one video driver is loaded

One of the benefits of Wayland is the ability to run multi-GPU multi-head sessions. It is also possible on some compositors (e.g. Sway) for users to do this with multiple GPU drivers (e.g. running a modern AMDGPU card and an older radeon card in the same machine). GDM is not a fan of this, but it can be coerced into behaving.

If this happens, a workaround is to temporarily blacklist the secondary GPU driver at load-time:

FILE /etc/modprobe.d/blacklist.conf
# Force AMDGPU to load first
blacklist nvidia
blacklist nouveau
blacklist radeon

Then, after GDM launches, switch to another tty and load the secondary GPU's driver. It will then be possible to switch back to GDM and start the WM, which if it can accept more than one GPU driver will utilize them.

GDM ignores my keyboard layout

GDM normally uses systemd to get the system keyboard configuration when available. If not, GDM will use the X configuration. However, the non-systemd GNOME profile on Gentoo defaults to OpenRC and Wayland, so none of this may work. GDM will then use a default us keyboard, which will make it difficult to type a password if this is not a desired layout.

In this case, configure the keyboard layout of the gdm user. This can be done opening Gnome settings (gnome-control-center). In the top right of the Region & Language panel, there is a Login Screen button which can be toggled to configure gdm language.

Unfortunately, this Login Screen button does not appear on every install (why?). If this is the case, change settings through command line.

For example, for a French keyboard, type as root:

root #su -s /bin/bash gdm
gdm $dbus-run-session gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'fr')]"
gdm $gsettings get org.gnome.desktop.input-sources sources
gdm $# you should see [('xkb', 'fr')] now
gdm $exit

If this previous solution does not work, patch Gnome shell so that it uses the keyboard defined in the session instead of the system one, which is as simple as creating the following file:

FILE /etc/portage/patches/gnome-base/gnome-shell/greeter-keyboard.patch
diff -Naur a/js/ui/status/keyboard.js b/js/ui/status/keyboard.js
--- a/js/ui/status/keyboard.js	2022-02-15 20:42:00.615129000 +0100
+++ b/js/ui/status/keyboard.js	2022-02-15 20:42:00.615129000 +0100
@@ -328,10 +328,7 @@
-        if (Main.sessionMode.isGreeter)
-            this._settings = new InputSourceSystemSettings();
-        else
-            this._settings = new InputSourceSessionSettings();
+        this._settings = new InputSourceSessionSettings();
         this._settings.connect('input-sources-changed', this._inputSourcesChanged.bind(this));
         this._settings.connect('keyboard-options-changed', this._keyboardOptionsChanged.bind(this));

and re-install Gnome shell:

root #emerge -1 gnome-shell

See also

  • GNOME/Guide — attempts to describe all aspects of GNOME, including installation, configuration, and usage.

External resources