From ArchWiki
Jump to: navigation, search

From GDM - GNOME Display Manager: "The GNOME Display Manager (GDM) is a program that manages graphical display servers and handles graphical user logins."

Display managers provide X Window System and Wayland users with a graphical login prompt.


GDM can be installed with the gdm package, and it is installed as part of the gnome group. To start GDM at boot time enable gdm.service.

If you would prefer to use legacy GDM which was used in GNOME 2 and has its own configuration utility, install the gdm-oldAUR package. Note that the rest of this article discusses current GDM, not legacy GDM, unless indicated otherwise.

You might also wish to install the following:

  • gdm3setup — An interface to configure GDM3, autologin options and change Shell theme || gdm3setupAUR


Autostarting applications with GDM

See Display manager#Autostarting. Note that adding scripts to /etc/gdm/Init no longer works, see the upstream bug report.

Log-in screen background image

Note: Since GNOME 3.16, GNOME Shell themes are now stored binary files (gresource).

Firstly, you need to extract the existing GNOME Shell theme to a folder in your home directory. You can do this using the following script:

if [ ! -d ${workdir}/theme ]; then
  mkdir -p ${workdir}/theme

for r in `gresource list $gst`; do
        gresource extract $gst $r >$workdir/${r#\/org\/gnome\/shell/}

Navigate to the created directory. You should find that the theme files have been extracted to it. Now copy your preferred background image to this directory.

Next, you need to create a file in the directory with the following content:

<?xml version="1.0" encoding="UTF-8"?>
  <gresource prefix="/org/gnome/shell/theme">

Replace filename with the filename of your background image.

Now, open the gnome-shell.css file in the directory and change the #lockDialogGroup definition as follows:

#lockDialogGroup {
  background: #2e3436 url(filename);
  background-size: [WIDTH]px [HEIGHT]px;
  background-repeat: no-repeat;

Set background-size to the resolution that GDM uses, this might not necessarily be the resolution of the image. For a list of display resolutions see Display resolution. Again, set filename to be the name of the background image.

Finally, compile the theme using the following command:

$ glib-compile-resources gnome-shell-theme.gresource.xml

Then copy the resulting gnome-shell-theme.gresource file to the /usr/share/gnome-shell directory.

Restart GDM - you should find that it is using your preferred background image.

For more information, please see the following forum thread.

DConf configuration

Some GDM settings are stored in a DConf database. They can be configured either by adding keyfiles to the /etc/dconf/db/gdm.d directory and then recompiling the GDM database by running dconf update as root or by logging into the GDM user on the system and changing the setting directly using the gsettings command line tool. Note that for the former approach, a GDM profile file is required - this must be created manually as it is no longer shipped upstream, see below:


For the latter approach, you can log into the GDM user with the command below:

# machinectl shell gdm@

Either create the following keyfile


and then recompile the GDM database or alternatively log in to the GDM user and execute the following:

$ gsettings set org.gnome.login-screen logo '/path/to/logo.png'

Changing the cursor theme

GDM disregards GNOME cursor theme settings and it also ignores the cursor theme set according to the XDG specification. To change the cursor theme used in GDM, either create the following keyfile


and then recompile the GDM database or alternatively log in to the GDM user and execute the following:

$ gsettings set org.gnome.desktop.interface cursor-theme 'theme-name'

Larger font for log-in screen

Click on the accessibility icon at the top right of the screen (a white circle with the silhouette of a person in the centre) and check the Large Text option.

To set a specific scaling factor, you can create the following keyfile:


and then recompile the GDM database or alternatively log in to the GDM user and execute the following:

$ gsettings set org.gnome.desktop.interface text-scaling-factor '1.25'

Turning off the sound

This tweak disables the audible feedback heard when the system volume is adjusted (via keyboard) on the login screen.

Either create the following keyfile:


and then recompile the GDM database or alternatively log in to the GDM user and execute the following:

$ gsettings set org.gnome.desktop.sound event-sounds 'false'

Make the power button interactive

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: Some button-* configuration options are no longer available from GDM 3.18. (Discuss in Talk:GDM#"Make the power button interactive" no longer possible with GDM 3.18)

The behaviour of the power buttons can be configured in GDM. The example below will configure the power and hibernate buttons to Show dialog:

Create the following keyfile:

[org/gnome/settings-daemon/plugins/power button]

and then recompile the GDM database.

Warning: Please note that the acpid daemon also handles the "power button" and "hibernate button" events. Running both systems at the same time may lead to unexpected behaviour.

Enabling tap-to-click

Tap-to-click is disabled in GDM (and GNOME) by default, but you can easily enable it with a dconf setting.

Note: If you want to do this under X, you have to first set up correct X server access permissions - see #Configure X server access permission.

To directly enable tap-to-click, use:

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

If you prefer to do this with a GUI, use:

# sudo -u gdm dconf-editor

To check the if it was set correctly, use:

$ sudo -u gdm gsettings get org.gnome.desktop.peripherals.touchpad tap-to-click

If you get the error dconf-WARNING **: failed to commit changes to dconf: Error spawning command line, make sure dbus is running:

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

Disable/Enable Accessibility Menu

To disable or enable the Accessibility Menu, set the following key in dconf editor:

# machinectl shell gdm@
# gsettings set org.gnome.desktop.interface toolkit-accessibility false
# exit

The menu is disabled when the key is false, enabled when it is true.

GDM keyboard layout

See Keyboard configuration in Xorg#Using X configuration files.

Tip: See Wikipedia:ISO 3166-1 for a list of keymaps.

GNOME Control Center

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: This is no longer applicable at least on Gnome Shell 3.20.2. (Discuss in Talk:GDM#)

If the package gnome-control-center is installed, the keyboard layout(s) can be configured using a graphical frontend. Start gnome-control-center and navigate to Keyboard -> Input Sources. Then, in the header bar, hit the Login Screen toggle button to configure the keyboard layout for GDM specifically.

GDM 2.x layout

Users of legacy GDM may need to follow the instructions below:

Edit ~/.dmrc:

Language=de_DE.UTF-8   # change to your default lang
Layout=de   nodeadkeys # change to your keyboard layout

Change the language

To change the GDM language, ensure that gnome-control-center is installed. Then, start gnome-control-center and choose Region & Language. In the header bar, check the Login Screen toggle button. Finally, click on Language and choose your language from the list. You will be prompted for your root password.

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: I could not get the method below to work with GDM 3.18.0 - tested on 2015-10-13. (Discuss in Talk:GDM#)

Alternatively, edit the file /var/lib/AccountsService/users/gdm and change the language line using the correct UTF-8 value for your language. You should see something similar to the text below:


Now just reboot your computer.

Once you have rebooted, if you look at the /var/lib/AccountsService/users/gdm file again, you will see that the language line is cleared — do not worry, the language change has been preserved.

Automatic login

To enable automatic login with GDM, add the following to /etc/gdm/custom.conf (replace username with your own):

# Enable automatic login for user
Tip: If GDM fails after adding these lines, comment them out from a TTY.

or for an automatic login with a delay:



Passwordless login

If you want to bypass the password prompt in GDM then simply add the following line on the first line of /etc/pam.d/gdm-password:

auth sufficient user ingroup nopasswdlogin

Then, add the group nopasswdlogin to your system. See Groups for group descriptions and group management commands.

Now, add your user to the nopasswdlogin group and you will only have to click on your username to login.

  • Do not do this for a root account.
  • You won't be able to change your session type at login with GDM anymore. If you want to change your default session type, you will first need to remove your user from the nopasswdlogin group.

Passwordless shutdown for multiple sessions

GDM uses polkit and logind to gain permissions for shutdown. You can shutdown the system when multiple users are logged in by setting:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
 "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"


  <action id="org.freedesktop.login1.power-off-multiple-sessions">
    <description>Shutdown the system when multiple users are logged in</description>
    <message>System policy prevents shutting down the system when other users are logged in</message>


You can find all available logind options (e.g. reboot-multiple-sessions) here.

Add or edit GDM sessions

Each session is a .desktop file located at /usr/share/xsessions/.

To add a new session:

1. Copy an existing .desktop file to use as a template for a new session:

$ cd /usr/share/xsessions
# cp gnome.desktop other.desktop

2. Modify the template .desktop file to open the required window manager:

# nano other.desktop

If you happen to have KDM installed in parallel, you can alternatively open the new session in KDM which will create the new .desktop file. Then return to using GDM and the new session will be available.

See also Display manager#Session configuration.

Enable root login in GDM

It is not advised to login as root, but if necessary you can edit /etc/pam.d/gdm-password and add the following line before the line auth required


auth            sufficient uid eq 0 quiet

The file should look something like this:


auth            sufficient uid eq 0 quiet
auth            sufficient uid >= 1000 quiet
auth            required

You should be able to login as root after restarting GDM.

Hide user from login list

The users for the gdm user list are gathered by AccountsService. It will automatically hide system users (UID < 1000). To hide ordinary users from the login list create or edit a file named after the user to hide in /var/lib/AccountsService/users/ to contain at least:


Setup default monitor settings

Some desktop environments store display settings in ~/.config/monitors.xml. xrandr commands are then generated on the base of the file content. GDM has a similar file stored in /var/lib/gdm/.config/monitors.xml.

If you have your monitors setup as you like (orientation, primary and so on) in ~/.config/monitors.xml and want GDM to honor those settings:

# cp ~/.config/monitors.xml /var/lib/gdm/.config/monitors.xml

Changes will take effect on logout. This is necessary because GDM does not respect xorg.conf.

Note: Wayland backend may be ignoring /var/lib/gdm/.config/monitors.xml file. See #Use Xorg backend to learn how to disable Wayland backend.

xrandr at login

If you want to run a script using xrandr that affects the login screen you must add a script in /etc/X11/xinit/xinitrc.d.

For example, to select automatically a external screen connected through HDMI:

if (xrandr | grep $EXTERNAL_OUTPUT | grep " connected "); then
    xrandr --output $INTERNAL_OUTPUT --off --output $EXTERNAL_OUTPUT --auto
    xrandr --output $INTERNAL_OUTPUT --auto

Configure X server access permission

You can use the xhost command to configure X server access permissions.

For instance, to grant GDM the right to access the X server, use the following command:

# xhost +SI:localuser:gdm


Failure to start with AMD Catalyst driver

Downgrade the xorg-server package or try to use another display manager like LightDM.

Failure on logout

If GDM starts up properly on boot, but fails after repeated attempts on logout, try adding this line to the daemon section of /etc/gdm/custom.conf:


Xorg 1.16

See Xorg#Rootless Xorg (v1.16).

Use Xorg backend

The Wayland backend is used by default and the Xorg backend is used only if the Wayland backend cannot be started. As the Wayland backend has been reported to cause problems for some users, use of the Xorg backend may be necessary. To use the Xorg backend by default, edit the /etc/gdm/custom.conf file and uncomment the following line:


Incomplete removal of gdm

After removing gdm, systemd may report the following:

user 'gdm': directory '/var/lib/gdm' does not exist

To remove this warning, login as root and delete the primary user "gdm" and then delete the group "gdm":

# userdel gdm
# groupdel gdm

Verify that gdm is successfully removed via pwck and grpck. To round it off, you may want to double-check no unowned files for gdm remain.

See also