LightDM

LightDM is Article description::a cross-desktop [[display manager whose aim is to be the standard display manager for the X server.]]

The key features (as listed by upstream) include:


 * A well-defined greeter API allowing multiple GUIs.
 * Support for all display manager use cases, with plugins where appropriate.
 * Low code complexity.
 * Fast performance.

Emerge
Install lightdm:

Configuration
The (global) configuration file for LightDM can be found at:



GTK
The GTK greeter configuration can be modified by manually editing the following file:

RazorQt
The RazorQt greeter currently does not offer any configuration options.

OpenRC
Set LightDM as the default display manager:

To start LightDM on boot, add dbus and xdm to the default runlevel. dbus is necessary because LightDM depends on it to pass messages:

To start LightDM now:

systemd
To start LightDM on boot:

To start LightDM now:

Command-line tool
LightDM includes a command-line tool,, which can be used to switch user sessions, lock the current seat, etc. To see a list of available commands, use the  option:

For example, to lock the current seat:

Running commands at log-in
A user can run some programs automatically when logging in using LightDM by adding commands in, which will be sourced by LightDM. For example:

Unlock GNOME Keyring
To unlock your GNOME Keyring automatically on login, edit  to look as follows. Note: Lines ending with the comment  should be added.

Locking your Screen with elogind After Suspend-Sleep
Sometimes you want to lock your screen after elogin triggers suspend or sleep. This can be done easily by doing the following:

Install light-locker:

Start light-locker once you startup X by putting light-locker & into or.

Create lock.sh under and be sure to add execute permissions to the file.

(Artix elogind Reference )

LightDM crashes upon first login if hostname changes during login
In some cases LightDM may crash when trying to log in for the first time if the hostname changes in the time between the boot and login (launchpad bug #1677058 ).

This may be encountered if is using the default settings to obtain the hostname from DHCP server and the hostname differs from the default one set on boot.

To disable NetworkManager hostname setting behavior, set the following line in  section of :

External resources

 * XDM