Difference between revisions of "SLiM"

From ArchWiki
Jump to: navigation, search
(avoid duplication of content, see also Help:Style)
(Multiple environments: corrected example)
(35 intermediate revisions by 18 users not shown)
Line 5: Line 5:
 
[[hu:SLiM]]
 
[[hu:SLiM]]
 
[[it:SLiM]]
 
[[it:SLiM]]
 +
[[ja:SLiM]]
 
[[ko:SLiM]]
 
[[ko:SLiM]]
 
[[pt:SLiM]]
 
[[pt:SLiM]]
Line 17: Line 18:
 
{{Article summary wiki|Display Manager}}
 
{{Article summary wiki|Display Manager}}
 
{{Article summary end}}
 
{{Article summary end}}
 
{{Note|It is not clear whether SLiM upstream development is in an active state, see [http://svn.berlios.de/svnroot/repos/slim/trunk/ChangeLog the changelog].}}
 
  
 
[http://slim.berlios.de/ SLiM] is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of [[GNOME]] or [[KDE]] and can help make a lighter system for users that like to use lightweight desktops like [[Xfce]], [[Openbox]], and [[Fluxbox]].
 
[http://slim.berlios.de/ SLiM] is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of [[GNOME]] or [[KDE]] and can help make a lighter system for users that like to use lightweight desktops like [[Xfce]], [[Openbox]], and [[Fluxbox]].
Line 30: Line 29:
 
=== Enabling SLiM ===
 
=== Enabling SLiM ===
  
SLiM can be loaded on startup by entering it in your DAEMONS array in {{ic|/etc/rc.conf}} or by modifying {{ic|/etc/inittab}}: see [[Display Manager#Loading the display manager]] for detailed instructions. If you use [[systemd]], just enable {{ic|slim.service}}. [[Dbus]] appears to be required since version 1.3.3 of SLiM.
+
{{Note|{{pkg|slim}} no longer has ConsoleKit support, but relies on systemd-logind, and the system being booted with systemd.}}
 +
 
 +
Enable the '''slim''' [[Daemons|daemon]]. With systemd, it is no longer possible to start slim using {{ic|inittab}}.
  
 
=== Single environments ===
 
=== Single environments ===
Line 45: Line 46:
 
#
 
#
  
exec [session-command]
+
exec <session-command>
 
}}
 
}}
  
SLiM reads the local {{ic|~/.xinitrc}} configuration and then launches the desktop according to what is in that file.  If you do not have a {{ic|~/.xinitrc}} file, you can use the skeleton file by:
+
Replace {{ic|<session-command>}} with the appropriate session command. Some examples of different desktop start commands:
 
+
$ cp /etc/skel/.xinitrc ~
+
 
+
Remember to make .xinitrc executable:
+
 
+
  chmod +x ~/.xinitrc
+
 
+
Replace {{ic|[session-command]}} with the appropriate session command. Some examples of different desktop start commands:
+
  
 
{{bc|
 
{{bc|
Line 73: Line 66:
 
For detailed instructions on how to start the various environments, refer to the appropriate wiki pages.
 
For detailed instructions on how to start the various environments, refer to the appropriate wiki pages.
  
{{Note|{{pkg|slim}} is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must '''no''' longer include {{ic|ck-launch-session}} in your .xinitrc or slim.conf login_cmd. You should still have {{ic|dbus-launch}} in your login_cmd, see [[#SLiM_and_Gnome_Keyring]], since this gives subprocesses of your session the correct permissions (e.g. to mount something with [[Wikipedia:GVFS|gvfs-mount]], like [[Pcmanfm]] does).}}
+
SLiM reads the local {{ic|~/.xinitrc}} configuration and then launches the desktop according to what is in that file. If you do not have a {{ic|~/.xinitrc}} file, you can use the skeleton file by:
 +
 
 +
$ cp /etc/skel/.xinitrc ~
 +
 
 +
Remember to make {{ic|~/.xinitrc}} executable:
 +
 
 +
chmod +x ~/.xinitrc
  
 
=== Autologin ===
 
=== Autologin ===
Line 85: Line 84:
  
 
Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.
 
Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.
 +
 +
=== Zsh ===
 +
{{Note|If you don't know what is zsh and you did not install it - ignore this paragraph.}}
 +
 +
The default login command will not initialize your environment correctly [http://www.edsel.nu/2010/06/04/slim-simple-login-manager-on-freebsd/ [source]]. Change the login_cmd line to:
 +
 +
#login_cmd          exec /bin/sh - ~/.xinitrc %session
 +
login_cmd          exec /bin/zsh -l ~/.xinitrc %session
  
 
=== Multiple environments ===
 
=== Multiple environments ===
Line 90: Line 97:
 
To be able to choose from multiple desktop environments, SLiM can be setup to log you into whichever you choose.
 
To be able to choose from multiple desktop environments, SLiM can be setup to log you into whichever you choose.
  
Put a case statement similar to this one in your {{ic|~/.xinitrc}} file and edit the sessions variable in {{ic|/etc/slim.conf}} to match the names that trigger the case statement. You can choose the session at login time by pressing F1. Note that this feature is experimental.
+
Put a case statement similar to this one in your {{ic|~/.xinitrc}} file and edit the sessions variable in {{ic|/etc/slim.conf}} to match the names that trigger the case statement. You can cycle through sessions at login time by pressing F1. Note that this feature is experimental.
  
 
{{bc|1=
 
{{bc|1=
Line 96: Line 103:
 
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample
 
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample
  
DEFAULT_SESSION=twm
+
DEFAULT_SESSION=kde
  
 
case $1 in
 
case $1 in
Line 121: Line 128:
 
esac
 
esac
 
}}
 
}}
+
 
Note that, in this script, the default option simply executes, e.g., exec icewm (if that is the default session), without icewmbg and icewmtray. You may want simply to repeat everything you've put under, e.g., icewm) again under *). When done use F1 to cycle through sessions in SLiM.
+
{{Note|<nowiki>In the latest version (1.3.5), slim does not preset any default session, so make sure that the 'DEFAULT_SESSION' variable in the script above is set to the session you want to start by default.
 +
For example, changing DEFAULT_SESSION=icewm will simply execute exec icewm without icewmbg and icewmtray. To execute all of the icewm) commands, repeat them under *).</nowiki>}}
  
 
=== Themes ===
 
=== Themes ===
Line 130: Line 138:
 
  # pacman -S slim-themes archlinux-themes-slim
 
  # pacman -S slim-themes archlinux-themes-slim
  
The {{Pkg|archlinux-themes-slim}} packages contains several different themes. Look in the directory of {{ic|/usr/share/slim/themes}} to see the themes available. Enter the theme name on the {{ic|current_theme}} line in {{ic|/etc/slim.conf}}:
+
The {{Pkg|archlinux-themes-slim}} packages contains several different themes ([http://imageshack.us/photo/my-images/27/slimthemes.png/ slimthemes.png]). Look in the directory of {{ic|/usr/share/slim/themes}} to see the themes available. Enter the theme name on the {{ic|current_theme}} line in {{ic|/etc/slim.conf}}:
  
 
  #current_theme      default
 
  #current_theme      default
Line 192: Line 200:
 
=== Shutdown, reboot, suspend, exit, launch terminal from SLiM ===
 
=== Shutdown, reboot, suspend, exit, launch terminal from SLiM ===
  
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, use the values in the username field, and the root password in the password field:
+
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, use the values in the username field, and the root password in the password field:
  
 
* To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit {{ic|/etc/slim.conf}} to change terminal preference)
 
* To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit {{ic|/etc/slim.conf}} to change terminal preference)
Line 202: Line 210:
 
=== SLiM init error with rc.d daemon ===
 
=== SLiM init error with rc.d daemon ===
  
If you initialize SLiM with {{ic|/etc/rc.conf}} inside the DAEMONS array and it fails to initialize it's most likely a lock file issue. SLiM creates a lock file in {{ic|/var/lock}} on each initialization, however, in most cases the lock folder in /var does not exist preventing SLiM from initializing. Check to make sure {{ic|/var/lock}} exists, if it does not you can create it by typing the following:
+
If you initialize SLiM with {{ic|/etc/rc.conf}} inside the DAEMONS array and it fails to initialize it's most likely a lock file issue. SLiM creates a lock file in {{ic|/var/lock}} on each initialization, however, in most cases the lock folder in {{ic|/var}} does not exist preventing SLiM from initializing. Check to make sure {{ic|/var/lock}} exists, if it does not you can create it by typing the following:
  
 
  # mkdir /var/lock/
 
  # mkdir /var/lock/
Line 208: Line 216:
 
=== Power-off error with Splashy ===
 
=== Power-off error with Splashy ===
  
If you use Splashy and SLiM, sometimes you can't power-off or reboot from menu in GNOME, Xfce, LXDE or others. Check your {{ic|/etc/slim.conf}} and {{ic|/etc/splash.conf}}; set the {{ic|1=DEFAULT_TTY=7}} same as {{ic|xserver_arguments vt07}}.
+
If you use Splashy and SLiM, sometimes you can't power-off or reboot from menu in GNOME, Xfce, LXDE or others. Check your {{ic|/etc/slim.conf}} and {{ic|/etc/splash.conf}}; set the {{ic|1=DEFAULT_TTY=7}} same as {{ic|xserver_arguments vt07}}.
  
 
=== Power-off tray icon fails ===
 
=== Power-off tray icon fails ===
Line 234: Line 242:
  
 
=== SLiM and Gnome Keyring ===
 
=== SLiM and Gnome Keyring ===
If you are using SLiM to launch a Gnome session and have trouble accessing your keyring, for example not being automatically authenticated on login, add the following lines to {{ic|/etc/pam.d/slim}} (as discussed [http://bugs.archlinux.org/task/18637 here]).
+
If you are using SLiM to launch a Gnome session and have trouble accessing your keyring, for example not being automatically authenticated on login, add the following lines to {{ic|/etc/pam.d/slim}} (as discussed [https://bugs.archlinux.org/task/18637 here]).
 
  auth      optional    pam_gnome_keyring.so
 
  auth      optional    pam_gnome_keyring.so
 
  session    optional    pam_gnome_keyring.so    auto_start
 
  session    optional    pam_gnome_keyring.so    auto_start
Line 243: Line 251:
 
If you use a screensaver you also have to add  
 
If you use a screensaver you also have to add  
 
  auth    optional        pam_gnome_keyring.so
 
  auth    optional        pam_gnome_keyring.so
to {{ic|/etc/pam.d/gnome-screensaver}} for example (replace gnome-screensaver with slimlock,slock,whatever you use). If you don't do that, your keyring is locked when screen is locked by your screensaver and not unlocked again after logging back in.
+
to {{ic|/etc/pam.d/gnome-screensaver}} for example (replace {{ic|gnome-screensaver}} with {{ic|slimlock}}, {{ic|slock}}, whatever you use). If you don't do that, your keyring is locked when screen is locked by your screensaver and not unlocked again after logging back in.
  
However, this fix alone no longer works since Gnome 2.30. Further changes are necessary as described [http://bugs.archlinux.org/task/18930 here]. Modifying the {{ic|login_cmd}} line in {{ic|/etc/slim.conf}}:
+
However, this fix alone no longer works since Gnome 2.30. Further changes are necessary as described [https://bugs.archlinux.org/task/18930 here]. Modifying the {{ic|login_cmd}} line in {{ic|/etc/slim.conf}}:
 
  login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1
 
  login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1
  
Line 251: Line 259:
  
 
As of GNOME 3.1, you need to add {{ic|dbus-launch}} after {{ic|ck-launch-session}} and edit {{ic|<nowiki>/etc/pam.d/{slim,passwd}</nowiki>}}, otherwise the keyring will not be automatically unlocked. I never tried it on 3.0, so maybe the above information about GNOME 3 is wrong.
 
As of GNOME 3.1, you need to add {{ic|dbus-launch}} after {{ic|ck-launch-session}} and edit {{ic|<nowiki>/etc/pam.d/{slim,passwd}</nowiki>}}, otherwise the keyring will not be automatically unlocked. I never tried it on 3.0, so maybe the above information about GNOME 3 is wrong.
 +
 +
As of GNOME 3.4, you need to edit {{ic|<nowiki>/etc/pam.d/{slim,passwd}</nowiki>}} as mentioned above, so that {{ic|<nowiki>/etc/pam.d/slim</nowiki>}} looks like:
 +
#%PAM-1.0
 +
auth            requisite      pam_nologin.so
 +
auth            required        pam_env.so
 +
auth            required        pam_unix.so
 +
auth            optional        pam_gnome_keyring.so
 +
account        required        pam_unix.so
 +
session        required        pam_limits.so
 +
session        required        pam_unix.so
 +
session        optional        pam_gnome_keyring.so auto_start
 +
password        required        pam_unix.so
 +
and {{ic|<nowiki>/etc/pam.d/passwd</nowiki>}}
 +
#%PAM-1.0
 +
password required pam_unix.so sha512 shadow nullok
 +
password optional pam_gnome_keyring.so
 +
As of 2012-10-13, {{ic|<nowiki>/etc/pam.d/gnome-screensaver</nowiki>}} already contains the {{ic|<nowiki>pam_gnome_keyring.so</nowiki>}} instruction.
 +
 +
The correct positioning of the {{ic|<nowiki>pam_gnome_keyring.so</nowiki>}} instructions were taken from [http://live.gnome.org/GnomeKeyring/Pam here].
 +
 +
After editing the above files, you need to edit {{ic|<nowiki>/etc/inittab</nowiki>}}. The above mentioned code
 +
login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1
 +
will work, but when you try to power off or reboot the system from GNOME menu it will drop you into the SLiM screen. To solve this problem, use the code below
 +
login_cmd exec dbus-launch --exit-with-session /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1
 +
{{ic|<nowiki>ck-launch-session</nowiki>}} is no longer necessary as stated [https://bbs.archlinux.org/viewtopic.php?pid=1099742#p1099742 here].
  
 
The solutions mentioned here and also further information are found [http://live.gnome.org/GnomeKeyring/Pam here].
 
The solutions mentioned here and also further information are found [http://live.gnome.org/GnomeKeyring/Pam here].
Line 264: Line 297:
 
  /usr/bin/awesome
 
  /usr/bin/awesome
  
After login check if there is only one gnome-keyring-daemon instance running (ps -A | grep gnome). If those lines are executed too early then you have 4 instances running which is not good.
+
After login check if there is only one gnome-keyring-daemon instance running ({{ic|ps -A | grep gnome}}). If those lines are executed too early then you have 4 instances running which is not good.
 
+
You also should notice that seahorse for example does not show any pkcs11 errors anymore and that your keyring is unlocked all the time and does not lock itself anymore. Finally gnome-keyring is fully functional like in Gnome. See also [https://bbs.archlinux.org/viewtopic.php?pid=1019845#p1019845 here].
+
 
+
=== SLiM and Environment Variables ===
+
If you have trouble with environment variables changing after a session is started, one cause could be the module pam_env.so, by default, reads the file {{ic|/etc/environment}} and sets up the environment accordingly.
+
 
+
For example: I use SLiM, which fires up a XFCE4 session upon valid authentication. When this is done my terminal(xfterm4) can't  print Unicode characters(LC_* environment variables has been defaulted/altered to "POSIX"). But when I start XFCE4 manually, like so: {{ic|startxfce4}}, Unicode characters on my terminal works fine.
+
 
+
This can be fixed by adding this to {{ic|/etc/environment}} or your user specific file: {{ic|$HOME/.pam_environment}}:
+
# You can change these to fit your preference, of course.
+
LANG="en_US.UTF-8"
+
LC_COLLATE="C"
+
  
Alternatively, you can modify the line in {{ic|/etc/pam.d/slim}} from:
+
You also should notice that seahorse for example does not show any pkcs11 errors anymore and that your keyring is unlocked all the time and does not lock itself anymore. Finally {{pkg|gnome-keyring}} is fully functional like in Gnome. See also [https://bbs.archlinux.org/viewtopic.php?pid=1019845#p1019845 here].
{{bc|session required pam_env.so}}
+
To:
+
{{bc|1=session required pam_env.so envfile=<yourfile>}}
+
Where <yourfile> is the name of the file you want PAM to recognize as your default environment file, when starting a new session from SLiM.
+
  
 
=== Setting DPI with SLiM ===
 
=== Setting DPI with SLiM ===
  
The Xorg server generally picks up the DPI but if it doesn't you can specify it to SLiM. If you set the DPI with the argument -dpi 96 in {{ic|/etc/X11/xinit/xserverrc}} it will not work with SLiM. To fix this change your {{ic|slim.conf}} from:
+
The Xorg server generally picks up the DPI but if it doesn't you can specify it to SLiM. If you set the DPI with the argument -dpi 96 in {{ic|/etc/X11/xinit/xserverrc}} it will not work with SLiM. To fix this change your {{ic|slim.conf}} from:
  
 
   xserver_arguments  -nolisten tcp vt07  
 
   xserver_arguments  -nolisten tcp vt07  
Line 296: Line 313:
 
=== Use a random theme ===
 
=== Use a random theme ===
  
Use the {{ic|current_theme}} variable as a comma separated list to specify a set from which to choose. Selection is random.
+
Use the {{ic|current_theme}} variable as a comma separated list to specify a set from which to choose. Selection is random.
  
 
===Move the whole session to another VT===
 
===Move the whole session to another VT===
Line 480: Line 497:
 
| session_shadow_color ||{{ic|#FFFFFF}}
 
| session_shadow_color ||{{ic|#FFFFFF}}
 
|}
 
|}
 
+
== Uninstallation ==
 +
To completely remove SLiM:
 +
{{bc| # pacman -Rns slim
 +
# rm /etc/systemd/system/display-manager.service
 +
}}
 
== See also ==
 
== See also ==
  
 
* [http://slim.berlios.de/ SLiM homepage]
 
* [http://slim.berlios.de/ SLiM homepage]
 
* [http://slim.berlios.de/manual.php SLiM documentation]
 
* [http://slim.berlios.de/manual.php SLiM documentation]

Revision as of 19:45, 26 January 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary end

SLiM is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of GNOME or KDE and can help make a lighter system for users that like to use lightweight desktops like Xfce, Openbox, and Fluxbox.

Installation

Install slim from the official repositories.

Configuration

Enabling SLiM

Note: slim no longer has ConsoleKit support, but relies on systemd-logind, and the system being booted with systemd.

Enable the slim daemon. With systemd, it is no longer possible to start slim using inittab.

Single environments

To configure SLiM to load a particular environment, edit your ~/.xinitrc to load your desktop environment:

#!/bin/sh

#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#

exec <session-command>

Replace <session-command> with the appropriate session command. Some examples of different desktop start commands:

exec awesome
exec dwm
exec startfluxbox
exec fvwm2
exec gnome-session
exec openbox-session
exec startkde
exec startlxde
exec startxfce4
exec enlightenment_start

For detailed instructions on how to start the various environments, refer to the appropriate wiki pages.

SLiM reads the local ~/.xinitrc configuration and then launches the desktop according to what is in that file. If you do not have a ~/.xinitrc file, you can use the skeleton file by:

$ cp /etc/skel/.xinitrc ~

Remember to make ~/.xinitrc executable:

chmod +x ~/.xinitrc

Autologin

To make SLiM automatically login as a specified user (without having to type a password) the following lines in /etc/slim.conf should be changed.

# default_user        simone

Uncomment this line, and change "simone" to the user to be logged into automatically.

# auto_login          no

Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.

Zsh

Note: If you don't know what is zsh and you did not install it - ignore this paragraph.

The default login command will not initialize your environment correctly [source]. Change the login_cmd line to:

#login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/zsh -l ~/.xinitrc %session

Multiple environments

To be able to choose from multiple desktop environments, SLiM can be setup to log you into whichever you choose.

Put a case statement similar to this one in your ~/.xinitrc file and edit the sessions variable in /etc/slim.conf to match the names that trigger the case statement. You can cycle through sessions at login time by pressing F1. Note that this feature is experimental.

# The following variable defines the session which is started if the user doesn't explicitly select a session
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample

DEFAULT_SESSION=kde

case $1 in
kde)
	exec startkde
	;;
xfce4)
	exec startxfce4
	;;
icewm)
	icewmbg &
	icewmtray &
	exec icewm
	;;
wmaker)
	exec wmaker
	;;
blackbox)
	exec blackbox
	;;
*)
	exec $DEFAULT_SESSION
	;;
esac
Note: In the latest version (1.3.5), slim does not preset any default session, so make sure that the 'DEFAULT_SESSION' variable in the script above is set to the session you want to start by default. For example, changing DEFAULT_SESSION=icewm will simply execute exec icewm without icewmbg and icewmtray. To execute all of the icewm) commands, repeat them under *).

Themes

Install the slim-themes package:

# pacman -S slim-themes archlinux-themes-slim

The archlinux-themes-slim packages contains several different themes (slimthemes.png). Look in the directory of /usr/share/slim/themes to see the themes available. Enter the theme name on the current_theme line in /etc/slim.conf:

#current_theme       default
current_theme       archlinux-simplyblack

To preview a theme run while an instance of the Xorg server is running by:

$ slim -p /usr/share/slim/themes/<theme name>

To close, type "exit" in the Login line and press Enter.

Additional theme packages can be found in the AUR.

Dual screen setup

You can customize the slim theme in /usr/share/slim/themes/<your-theme>/slim.theme to turn these percents values. The box itself is 450 pixels by 250 pixels:

input_panel_x           50%
input_panel_y           50%

into pixels values:

# These settings set the "archlinux-simplyblack" panel in the center of a 1440x900 screen
input_panel_x           495
input_panel_y           325
# These settings set the "archlinux-retro" panel in the center of a 1680x1050 screen
input_panel_x           615
input_panel_y           400

If your theme has a background picture you should use the background_style setting ('stretch', 'tile', 'center' or 'color') to get it correctly displayed. Have a look at the very simple and clear official documentation about slim themes for further details.

Other options

A few things you might like to try.

Changing the cursor

If you want to change the default X cursor to a newer design, the slim-cursorAUR package is available.

After installing, edit /etc/slim.conf and uncomment the line:

cursor   left_ptr

This will give you a normal arrow instead. This setting is forwarded to xsetroot -cursor_name. You can look up the possible cursor names here or in /usr/share/icons/<your-cursor-theme>/cursors/.

To change the cursor theme being used at the login screen, make a file named /usr/share/icons/default/index.theme with this content:

[Icon Theme]
Inherits=<your-cursor-theme>

Replace <your-cursor-theme> with the name of the cursor theme you want to use (e.g. whiteglass).

Match SLiM and Desktop Wallpaper

To share a wallpaper between SLiM and your desktop, rename the used theme background, then create a link from your desktop wallpaper file to the default SLiM theme:

# mv /usr/share/slim/themes/default/background.jpg{,.bck}
# ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg

Shutdown, reboot, suspend, exit, launch terminal from SLiM

You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, use the values in the username field, and the root password in the password field:

  • To launch a terminal, enter console as the username (defaults to xterm which must be installed separately... edit /etc/slim.conf to change terminal preference)
  • For shutdown, enter halt as the username
  • For reboot, enter reboot as the username
  • To exit to bash, enter exit as the username
  • For suspend, enter suspend as the username (suspend is disabled by default, edit /etc/slim.conf as root to uncomment the suspend_cmd line and, if necessary modify the suspend command itself (e.g. change /usr/sbin/suspend to sudo /usr/sbin/pm-suspend))

SLiM init error with rc.d daemon

If you initialize SLiM with /etc/rc.conf inside the DAEMONS array and it fails to initialize it's most likely a lock file issue. SLiM creates a lock file in /var/lock on each initialization, however, in most cases the lock folder in /var does not exist preventing SLiM from initializing. Check to make sure /var/lock exists, if it does not you can create it by typing the following:

# mkdir /var/lock/

Power-off error with Splashy

If you use Splashy and SLiM, sometimes you can't power-off or reboot from menu in GNOME, Xfce, LXDE or others. Check your /etc/slim.conf and /etc/splash.conf; set the DEFAULT_TTY=7 same as xserver_arguments vt07.

Power-off tray icon fails

If your power off tray icon fails, it could be due to not having root privileges. To start a tray icon with root privileges, be sure to have SLiM start the program. Edit /etc/slim.conf as follows:

sessionstart_cmd 	/path/to/tray/icon/program &

Login information with SLiM

By default, SLiM fails to log logins to utmp and wtmp which causes who, last, etc. to misreport login information. To fix this edit your slim.conf as follows:

 sessionstart_cmd    /usr/bin/sessreg -a -l $DISPLAY %user
 sessionstop_cmd     /usr/bin/sessreg -d -l $DISPLAY %user

Custom SLiM Login Commands

You can also use the sessionstart_cmd/sessionstop_cmd in /etc/slim.conf to log specific infomation, such as the session, user, or theme used by slim:

 sessionstop_cmd /usr/bin/logger -i -t ASKAPACHE "(sessionstop_cmd: u:%user s:%session t:%theme)"
 sessionstart_cmd /usr/bin/logger -i -t ASKAPACHE "(sessionstart_cmd: u:%user s:%session t:%theme)"

Or if you want to play a song when slim loads (and you have the beep program installed)

 sessionstart_cmd /usr/bin/beep -f 659 -l 460 -n -f 784 -l 340 -n -f 659 -l 230 -n -f 659 -l 110

SLiM and Gnome Keyring

If you are using SLiM to launch a Gnome session and have trouble accessing your keyring, for example not being automatically authenticated on login, add the following lines to /etc/pam.d/slim (as discussed here).

auth       optional    pam_gnome_keyring.so
session    optional    pam_gnome_keyring.so    auto_start

You also have to add to /etc/pam.d/passwd:

password        optional        pam_gnome_keyring.so

If you use a screensaver you also have to add

auth    optional        pam_gnome_keyring.so

to /etc/pam.d/gnome-screensaver for example (replace gnome-screensaver with slimlock, slock, whatever you use). If you don't do that, your keyring is locked when screen is locked by your screensaver and not unlocked again after logging back in.

However, this fix alone no longer works since Gnome 2.30. Further changes are necessary as described here. Modifying the login_cmd line in /etc/slim.conf:

login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1

As of GNOME 3, simply adding dbus-launch after ck-launch-session will work, without needing to edit /etc/pam.d/slim.

As of GNOME 3.1, you need to add dbus-launch after ck-launch-session and edit /etc/pam.d/{slim,passwd}, otherwise the keyring will not be automatically unlocked. I never tried it on 3.0, so maybe the above information about GNOME 3 is wrong.

As of GNOME 3.4, you need to edit /etc/pam.d/{slim,passwd} as mentioned above, so that /etc/pam.d/slim looks like:

#%PAM-1.0
auth            requisite       pam_nologin.so
auth            required        pam_env.so
auth            required        pam_unix.so
auth            optional        pam_gnome_keyring.so
account         required        pam_unix.so
session         required        pam_limits.so
session         required        pam_unix.so
session         optional        pam_gnome_keyring.so auto_start
password        required        pam_unix.so

and /etc/pam.d/passwd

#%PAM-1.0
password	required	pam_unix.so sha512 shadow nullok
password	optional	pam_gnome_keyring.so

As of 2012-10-13, /etc/pam.d/gnome-screensaver already contains the pam_gnome_keyring.so instruction.

The correct positioning of the pam_gnome_keyring.so instructions were taken from here.

After editing the above files, you need to edit /etc/inittab. The above mentioned code

login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1

will work, but when you try to power off or reboot the system from GNOME menu it will drop you into the SLiM screen. To solve this problem, use the code below

login_cmd exec dbus-launch --exit-with-session /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1

ck-launch-session is no longer necessary as stated here.

The solutions mentioned here and also further information are found here.

If you have problems keeping the keyring unlocked for longer sessions, there is another thing that Gnome does: Look at /etc/xdg/autostart/{gnome-keyring-gpg.desktop, gnome-keyring-pkcs11.desktop, gnome-keyring-secrets.desktop, gnome-keyring-ssh.desktop}.

Append the following lines to .xinitrc just before you start your wm (example here is awesome wm):

/usr/bin/gnome-keyring-daemon --start --components=gpg
/usr/bin/gnome-keyring-daemon --start --components=pkcs11
/usr/bin/gnome-keyring-daemon --start --components=secrets
/usr/bin/gnome-keyring-daemon --start --components=ssh
/usr/bin/awesome

After login check if there is only one gnome-keyring-daemon instance running (ps -A ). If those lines are executed too early then you have 4 instances running which is not good.

You also should notice that seahorse for example does not show any pkcs11 errors anymore and that your keyring is unlocked all the time and does not lock itself anymore. Finally gnome-keyring is fully functional like in Gnome. See also here.

Setting DPI with SLiM

The Xorg server generally picks up the DPI but if it doesn't you can specify it to SLiM. If you set the DPI with the argument -dpi 96 in /etc/X11/xinit/xserverrc it will not work with SLiM. To fix this change your slim.conf from:

 xserver_arguments   -nolisten tcp vt07 

to

 xserver_arguments   -nolisten tcp vt07 -dpi 96

Use a random theme

Use the current_theme variable as a comma separated list to specify a set from which to choose. Selection is random.

Move the whole session to another VT

Lets say you have commented out tty terminals 3-6 as you may not use them. (You may use screen and therefore only need one terminal) So, to move the X-Server you need to change one number in the /etc/slim.conf file. Just a few lines down you should see:

xserver_arguments -nolisten tcp vt07

Simply change the vt07 to lets say vt03 as there is no agetty started there.

Automatically mount your encrypted /home on login

You can use pam_mount.

All Slim Options

Here is a list of all the slim configuration options and their default values.

Note: welcome_msg allows 2 variables %host and %domain
sessionstart_cmd allows %user (execd right before login_cmd) and it is also allowed in sessionstop_cmd
login_cmd allows %session and %theme

Uninstallation

To completely remove SLiM:

 # pacman -Rns slim
 # rm /etc/systemd/system/display-manager.service

See also