#Multiseat x session startx how to
#Multiseat x session startx manual

desktop, and not running systemd, for better or worse you're using a less-supported configuration. (But you may still use ~/.xsessionrc.If you're running an up-to-date GNOME/KDE/etc. If you login with gdm3 and choose a GNOME session, the ~/.xsession file will be ignored completely.

#Multiseat x session startx how to

(If you are unsure how to determine this, consult your WM or DE documentation, or stick with the simpler ~/.xsessionrc.)įinally, note that the ~/.xsession file is only read if you are using a Debian X session. The final command in the script should be an exec which runs your WM's or DE's regular start command. Here is a simplistic ~/.xsession example: xsetroot -solid grayĪs with ~/.xsessionrc, any X client applications that you run before the WM or DE should either be naturally short-lived, or launched explicitly in the background. Therefore, if you use it, you must ensure that it launches your desired window manager (WM) or desktop environment (DE). This file, if it exists, is used instead of the system-wide default x-session-manager or x-window-manager. If you selected a GNOME session, additional configuration will be read from the ~/.gnomerc file, if it exists.Ī more advanced alternative is to use the ~/.xsession file. Also note that because ~/.xsessionrc is read very early, any settings you place here may be overridden by your window manager or desktop environment, later in the login sequence. xmodmap or xset or xsetbg commands), or that you run it in the background by terminating the command with the shell's & operator. If you choose to run an X client program, make sure it either terminates quickly on its own (e.g. If you choose to dot in one of your regular shell dot files, make sure it does not use bash specific features, zsh specific features, ksh specific features, etc. You may directly run X client programs: xclock -geometry +0+0 & You may dot in some other POSIX shell configuration file: if then. You may place environment variable definitions here, directly: export SOME_VAR='some value' There are typically three kinds of commands you may wish to use in this file: You should avoid using features that are not supported in POSIX sh. It is read by a POSIX shell ( /bin/sh, typically provided by dash). The simplest way is to create a ~/.xsessionrc file, which will be used by all X session types. User configuration may be done in a few different ways.

Otherwise, if the /usr/bin/x-terminal-emulator command exists, run it. Otherwise, if the /usr/bin/x-window-manager command exists, run it.

Otherwise, if the /usr/bin/x-session-manager command exists, run it. Otherwise, if the user has a ~/.xsession or ~/.Xsession file, run it. If a specific session was selected in the DM (GDM, KDM, WDM, LightDM.If the user has a ~/.xsessionrc file, read it.

#Multiseat x session startx manual

The Debian reference manual describes how the defaults work: Administrators may edit the scripts, though caution is advised if you are not comfortable with shell programming. These scripts are all dotted in by a single /bin/sh shell, in the order determined by sorting their names. System-wide configuration of the Debian X session consists mainly of options inside the /etc/X11/Xsession.options file, and scripts inside the /etc/X11/Xsession.d directory.

If you select something other than a Debian X session, the remainder of this page may not apply completely. Some display managers may offer a choice of session types. The standard ways to run a Debian X session are to run startx from a console login, or to login through a DisplayManager such as lightdm, gdm3 or xdm. The man pages Xsession(5) and Xsession.options(5) offer technical descriptions. There are a few different types of X sessions this page describes the default Debian X session, and how to work with it. When you start the X Window System on Debian, an X session will be created.