GDM is a system service that is responsible for providing graphical logins and managing local and remote displays.
![[Note]](../images/note.png)
Development versions of BLFS may not build or run some packages properly if LFS or dependencies have been updated since the most recent stable versions of the books.
Download (HTTP): https://download.gnome.org/sources/gdm/47/gdm-47.0.tar.xz
Download MD5 sum: 0312497290b26525e14fbc153f1a87f2
Download size: 916 KB
Estimated disk space required: 37 MB
Estimated build time: 0.2 SBU
AccountsService-23.13.9, DConf-0.40.0, libcanberra-0.30 (built after GTK+-3.24.43), and Linux-PAM-1.7.0
It is recommended to have a dedicated user and group to take
control of the gdm
daemon after it is started. Issue the following commands as the
root user:
groupadd -g 21 gdm &&
useradd -c "GDM Daemon Owner" -d /var/lib/gdm -u 21 \
-g gdm -s /bin/false gdm &&
passwd -ql gdm
Install GDM by running the following commands:
sed -e 's@systemd@elogind@' \
-e '/elogind/isession required pam_loginuid.so' \
-i data/pam-lfs/gdm-launch-environment.pam &&
mkdir build &&
cd build &&
meson setup .. \
--prefix=/usr \
--buildtype=release \
-D gdm-xsession=true \
-D run-dir=/run/gdm \
-D logind-provider=elogind \
-D systemd-journal=false \
-D systemdsystemunitdir=no \
-D systemduserunitdir=no &&
ninja
This package does not come with a usable test suite.
Now, as the root user:
ninja install
--buildtype=release:
Specify a buildtype suitable for stable releases of the package, as
the default may produce unoptimized binaries.
-D initial-vt=7: Use this switch to
make GDM start on VT7 instead of
the first free VT.
-D default-pam-config=lfs: Use this
switch if you did not create the /etc/lfs-release file or distribution auto
detection will fail and you will be unable to use GDM.
-D gdm-xsession=true: This
enables the installation of the GDM Xsession file.
The GDM daemon is configured using the /etc/gdm/custom.conf file. Default values are
stored in GSettings in the gdm.schemas file. It is recommended that
end-users modify the /etc/gdm/custom.conf file because the schemas
file may be overwritten when the user updates their system to
have a newer version of GDM.
On some systems with NVIDIA GPUs, GDM will hide Wayland sessions
by default. This is often done to prevent users from encountering
problems with buggy drivers, which can result in system lockups,
application crashes, power management problems, and graphics
slowdowns. If you have an NVIDIA GPU and still want to try
running Wayland sessions anyway, execute the following command as
the root user:
ln -s /dev/null /etc/udev/rules.d/61-gdm.rules
To start gdm
automatically when the system is switched to runlevel 5, install
the /etc/rc.d/init.d/xdm script and
the /etc/sysconfig/xdm
configuration file included in the blfs-bootscripts-20241209 package and
adjust /etc/inittab by running as
the root user:
make install-gdm
In order to permanently set the default runlevel to 5, starting
the gdm greeter
screen automatically, you can modify /etc/inittab. As the root user:
sed /initdefault/s/3/5/ -i /etc/inittab
GDM will suspend the system when the greeter screen has been
running for a while without any interactive input. If you want to
disable auto-suspending for any reason (for example if the system
is hosting some services besides functioning as a desktop
system), as the root user, issue:
su gdm -s /bin/bash \
-c "dbus-run-session \
gsettings set org.gnome.settings-daemon.plugins.power \
sleep-inactive-ac-type \
nothing"