Man page 5 : Xsession

Xsessionmay optionally be passed a single argument indicating the type of X session to be started. It is up to the display manager to set the argument. To pass Xsessionan argument from

startx or

R xinit , /etc/X11/Xsession(or /etc/X11/xinit/xinitrc ) must be called explicitly with a path, as in

startx /etc/X11/Xsession

R failsafe . By default, three different arguments are supported:

failsafe

    invokes a session consisting solely of an

R x-terminal-emulator (1) (no window manager is launched). If the

x-terminal-emulator program cannot be found, the session exits. The (oqfailsafe(cq argument is ignored if there is no (oqallow-failsafe(cq line in Xsession.options .

default

    produces the same behavior as if no session type argument had been given at all.

• program
      starts programif it can be found in the $PATH. This is usually a session manager or a very featureful window manager. If programis not found, the Xsessionscript proceeds with its default behavior. This argument is ignored if there is no (oqallow-user-xsession(cq line in Xsession.options . (If the administrator does not want users writing their own .xsessionfiles, it makes little sense to permit them to specify the names of arbitrary programs to run.) Note that the restriction may be easy to bypass, e.g. by using a .gnomercfile instead.

Initially, Xsessionperforms some housekeeping. It declares a set of built-in functions (see « BUILT-IN SHELL FUNCTIONS » below) and variables, then attempts to create a log file for the X session, or append to an existing one. Historically this is called an (oqerror(cq file, but it catches all sorts of diagnostic output from various X clients run in the user's session, not just error messages. If it is impossible to write to an error file, the script (and thus the X session) aborts. For convenience, once the error file is successfully opened, Xsessionreports the fact that the session has started, the invoking username, and the date to the error file. This makes it easier to discern which X session produced a particular line of output in the file.

Xsessionnext confirms that its script directory, Xsession.d , exists. If it does not, the script aborts. After the script directory is confirmed to be present, Xsessionuses

R run-parts (1) to identify files in that directory that should be sourced (executed) in the shell's environment. Only files named in a certain way are sourced; see the

run-parts manual page for a description of valid characters in the filename. (This restriction enables the administrator to move experimental or problematic files out of the way of the script but keep them in an obvious place, for instance by renaming them with (oq.old(cq or (oq
oken(cq appended to the filename.)

Five shell script portions are supplied by default to handle the details of the session startup procedure.

• /etc/X11/Xsession.d/20x11-common_process-args
      Arguments are processed as described in « SESSION TYPES » above. The startup program, if one is identified at this point, is merely stored for later reference, and not immediately executed.
• /etc/X11/Xsession.d/30x11-common_xresources
      X resources are merged.

run-parts is again used, this time to identify files in the /etc/X11/Xresourcesdirectory that should be processed with (oqxrdb -merge(cq. Next, if the line (oqallow-user-resources(cq is present in Xsession.options , the user's $HOME/.Xresourcesfile is merged in the same way.

• /etc/X11/Xsession.d/40x11-common_xsessionrc
      Source global environment variables. This script will source anything in $HOME/.xsessionrc if the file is present. This allows the user to set global environment variables for their X session, such as locale information.
• /etc/X11/Xsession.d/50x11-common_determine-startup
      Determine startup program. The X client to launch as the controlling process (the one that, upon exiting, causes the X server to exit as well) is determined next. If a program or failsafe argument was given and is allowed (see above), it is used as the controlling process. Otherwise, if the line (oqallow-user-xsession(cq is present in Xsession.options , a user-specified session program or script is used. In the latter case, two historically popular names for user X session scripts are searched for: $HOME/.xsession and $HOME/.Xsession (note the difference in case). The first one found is used. If the script is not executable, it is marked to be executed with the Bourne shell interpreter,

R sh . Finally, if none of the above succeeds, the following programs are searched for: /usr/bin/x-session-manager , /usr/bin/x-window-manager , and /usr/bin/x-terminal-emulator . The first one found is used. If none are found, Xsessionaborts with an error.

• /etc/X11/Xsession.d/90x11-common_ssh-agent
      Start

R ssh-agent (1), if needed. If the line (oquse-ssh-agent(cq is present in Xsession.options , and no SSH agent process appears to be running already,

ssh-agent is marked to be used to execute the startup program determined previously.

Note: this functionality may move to the ssh package in the future.

• /etc/X11/Xsession.d/99x11-common_start
      Start the X session. The startup program is executed, inside a Bourne shell if it is not executable, and inside an ssh-agent if necessary. The shell's

exec command is used to spare a slot in the process table.

Of course, any of the existing files can be edited in place.

Because the order in which the various scripts in /etc/X11/Xsession.dare executed is important, files to be added to this directory should have a well-formed name. The following format is recommended:

* a two-digit number denoting sequence;

* the name of the package providing the script (or (oqcustom(cq for locally-created scripts);

* an underscore;

* a description of the script's basic function, using only characters allowed by

R run-parts .

Here is an example of how one might write a script, named 40custom_load-xmodmap , to invoke

R xmodmap (1):

SYSMODMAP="/etc/X11/Xmodmap"
 USRMODMAP="$HOME/.Xmodmap"

if [ -x /usr/bin/X11/xmodmap ]; then if [ -f "$SYSMODMAP" ]; then xmodmap "$SYSMODMAP" fi fi

if [ -x /usr/bin/X11/xmodmap ]; then if [ -f "$USRMODMAP" ]; then xmodmap "$USRMODMAP" fi fi

Those writing scripts for Xsessionto execute should avail themselves of its built-in shell functions, described below.

message is used for communicating with the user. It is a wrapper for the

R echo (1) command and relies upon

echo for its argument processing. This function may be given an arbitrarily long message string, which is formatted to the user's terminal width (breaking lines at whitespace) and sent to standard error. If the DISPLAYenvironment variable is set and the

R xmessage (1) program is available,

xmessage is also used to display the message.

message_nonl is used for communicating with the user when a trailing newline is undesirable; it omits a trailing newline from the message text. It otherwise works as

R message .

errormsg is used for indicating an error condition and aborting the script. It works as

R message , above, except that after displaying the message, it will exit Xsessionwith status 1.