SLiM

SLiM (Simple Login Manager) is a desktop-independent graphical display manager. Being fast and having only a few dependencies, it is a popular choice amongst users of lightweight window managers.

Installation
Install :

OpenRC
Set SLiM as your default display manager:

To start SLiM on boot, add xdm to your default runlevel:

To start SLiM now:

systemd
To start SLiM on boot:

To start SLiM now:

Upstream-Style configuration
Make this section look like this:

Then follow wiki pages to setup window manager of your choice that starts.

Default configuration - no default session
Most global configuration is done in.

By default, SLiM is configured to make all sessions in accessible — you can cycle through them by pressing the  key. This behavior is acquired by setting the options below:

When no other changes are made, users will need to press while logging-in to select the desired session. In following sections there are described several methods of setting one session as the default one.

Setting a global default session
You can set a default session for all users of the computer, by setting the XSESSION variable. To do this, create and edit file.

After saving the file run:

Setting a default session for one user
Besides (or instead of) setting a global default session, you can let every user choose his default session.

There are three approaches. You can either:
 * use the SLiM session script to trigger session script from
 * use the SLiM session script to trigger user-created session script
 * force users to take care of setting everything by themselves

The first and second possibilities are generally preferred. However, if for any reason you do not want to set any defaults, you may choose the third approach.

Per-user default session using bundled session files
The simplest way to set a default session for one user is to make a symbolic link from the session file to

An alternative is to put session command in the file:

You will only need to make sure the file is executable:

Per-user default session using the customized ~/.xsession file
Sometimes you need to customize the launcher script, e.g. to run other programs before starting the window manager or to start WM with a customized command. The method above does not allow such modifications, but it can be achieved by using default session script (instead of the one provided by window manager) and launching WM through the file.

To run your sessions this way, make sure you have no global default session set (or set it to XSESSION="custom" in like described above). Then edit your file, putting your WM launcher at the end.

The file may look like this:

You may also look at the WM session files in to find "how things are done".

Finally, remember to make sure the file is executable:

Per-user default session without using any default session files
If you do not like any defaults from and, you can let your users set everything by themselves. It is generally not a good idea, but sometimes you may need it.

Start by editing in the following way:

In the sessions line you may put the names of window managers you are planning to use.

Then create and edit file, which may look as below:

Finally make sure the file is executable:

Theme selection
Theme selection is done by changing the following line:

You can easily find what themes are available on your system:

You can preview a theme by running the following command while Xorg is running:

NumLock state on login
The NumLock key can be turned on or off by default:

Autologin
Change $USER to the user name you want to log in as.

for me i would insert default_user       666threesixes666

If you have  this is easiest quickest automated way to insert this.

Unlock keyrings
The following section will describe how to make SLiM automatically unlock different keychains automatically when you log in.

GNOME Keyring
First make sure you have (include  if you want a GUI). To configure SLiM to unlock your GNOME Keyring automatically you have to edit its PAM configuration file. To do so open /etc/pam.d/slim and modify it to look similar to the text below. Lines ending with comment "#keyring" should be added.

Once this change has been made your keyring should be automatically unlocked next time you log in.

Failed to connect to socket /var/run/dbus/system_bus_socket:
This error is caused when dbus hasn't been started. It is possible that it wasn't added to the default run level. To fix this type the following:

This will ensure that dbus is running when you boot up your computer. It may be that this has already been added by other WM, but I had to do this when using awesome WM.