MAN page from WhiteBox xscreensaver-4.18-5.rhel4.2.WB1.x86_64.rpm


Section: User Commands (1)
Updated: 14-Aug-2004 (4.18)


xscreensaver - extensible screen saver framework, plus locking 


xscreensaver[-display host:display.screen] [-verbose] [-no-capture-stderr] [-no-splash] 


The xscreensaver program waits until the keyboard and mouse have been idle for a period, and then runs a graphics demo chosen at random. It turns off as soon as there is any mouse or keyboard activity.

This program can lock your terminal in order to prevent others from using it,though its default mode of operation is merely to display pretty pictures onyour screen when it is not in use.

It also provides configuration and control of your monitor's power-savingfeatures. 


For the impatient, try this:

xscreensaver &xscreensaver-demo

Thexscreensaver-demo(1)program pops up a dialog box that lets you configure the screen saver,and experiment with the various display modes.

Note:unlikexlock(1),xscreensaver has a client-server model: the xscreensaver program is adaemon that runs in the background; it is controlled by the foregroundxscreensaver-demo(1)andxscreensaver-command(1)programs. 


The easiest way to configure xscreensaver is to simply run thexscreensaver-demo(1)program, and change the settings through the GUI. The rest of thismanual page describes lower level ways of changing settings.

I'll repeat that because it's important:

The easy way to configure xscreensaver is to run the xscreensaver-demo(1)program. You shouldn't need to know any of the stuff described in this manual unless you are trying to do something tricky,like customize xscreensaver for site-wide use or something.

Options to xscreensaver are stored in one of two places: in a .xscreensaver file in your home directory; or in the X resourcedatabase. If the .xscreensaver file exists, it overrides any settingsin the resource database.

The syntax of the .xscreensaver file is similar to that ofthe .Xdefaults file; for example, to set the timeout paramterin the .xscreensaver file, you would write the following:

timeout: 5

whereas, in the .Xdefaults file, you would write

xscreensaver.timeout: 5

If you change a setting in the .xscreensaver file while xscreensaveris already running, it will notice this, and reload the file. (The file willbe reloaded the next time the screen saver needs to take some action, such asblanking or unblanking the screen, or picking a new graphics mode.)

If you change a setting in your X resource database, or if you wantxscreensaver to notice your changes immediately instead of the next timeit wakes up, then you will need to reload your .Xdefaults file,and then tell the running xscreensaver process to restart itself, like so:

xrdb < ~/.Xdefaultsxscreensaver-command -restart

If you want to set the system-wide defaults, then make your edits tothe xscreensaver app-defaults file, which should have been installedwhen xscreensaver itself was installed. The app-defaults file willusually be named /usr/lib/X11/app-defaults/XScreenSaver, but differentsystems might keep it in a different place (for example,/usr/openwin/lib/app-defaults/XScreenSaver on Solaris.)

When settings are changed in the Preferences dialog box (see above)the current settings will be written to the .xscreensaver file.(The .Xdefaults file and the app-defaults file will never bewritten by xscreensaver itself.)

timeout (class Time)
The screensaver will activate (blank the screen) after the keyboard andmouse have been idle for this many minutes. Default 10 minutes.
cycle (class Time)
After the screensaver has been running for this many minutes, the currentlyrunning graphics-hack sub-process will be killed (with SIGTERM), and anew one started. If this is 0, then the graphics hack will never be changed:only one demo will run until the screensaver is deactivated by user activity.Default 10 minutes.
lock (class Boolean)
Enable locking: before the screensaver will turn off, it will require you to type the password of the logged-in user (really, the person who ranxscreensaver), or the root password. (Note: this doesn't work if thescreensaver is launched byxdm(1)because it can't know the user-id of the logged-in user. See the ``Using XDM(1)'' section, below.
lockTimeout (class Time)
If locking is enabled, this controls the length of the ``grace period''between when the screensaver activates, and when the screen becomes locked.For example, if this is 5, and -timeout is 10, then after 10 minutes,the screen would blank. If there was user activity at 12 minutes, no passwordwould be required to un-blank the screen. But, if there was user activityat 15 minutes or later (that is, -lock-timeout minutes after activation) then a password would be required. The default is 0, meaningthat if locking is enabled, then a password will be required as soon as the screen blanks.
passwdTimeout (class Time)
If the screen is locked, then this is how many seconds the password dialog boxshould be left on the screen before giving up (default 30 seconds.) Thisshould not be too large: the X server is grabbed for the duration that thepassword dialog box is up (for security purposes) and leaving the server grabbed for too long can cause problems.
dpmsEnabled (class Boolean)
Whether power management is enabled.
dpmsStandby (class Time)
If power management is enabled, how long until the monitor goes solid black.
dpmsSuspend (class Time)
If power management is enabled, how long until the monitor goes intopower-saving mode.
dpmsOff (class Time)
If power management is enabled, how long until the monitor powers downcompletely. Note that these settings will have no effect unless boththe X server and the display hardware support power management; not all do. See the Power Management section, below, for more information.
visualID (class VisualID)
Specify which X visual to use by default. (Note carefully that this resourceis called visualID, not merely visual; if you set the visualresource instead, things will malfunction in obscure ways for obscure reasons.)

Legal values for the VisualID resource are:

Use the screen's default visual (the visual of the root window.) This is the default.
Use the visual which supports the most colors. Note, however, that thevisual with the most colors might be a TrueColor visual, which does notsupport colormap animation. Some programs have more interesting behaviorwhen run on PseudoColor visuals than on TrueColor.
Use a monochrome visual, if there is one.
Use a grayscale or staticgray visual, if there is one and it has more thanone plane (that is, it's not monochrome.)
Use the best of the color visuals, if there are any.
Use the visual that is best for OpenGL programs. (OpenGL programs havesomewhat different requirements than other X programs.)
where class is one of StaticGray, StaticColor, TrueColor, GrayScale, PseudoColor, or DirectColor.Selects the deepest visual of the given class.
where number (decimal or hex) is interpreted as a visual id number, as reported by thexdpyinfo(1)program; in this way you can have finer control over exactly which visualgets used, for example, to select a shallower one than would otherwisehave been chosen.

Note that this option specifies only the default visual that willbe used: the visual used may be overridden on a program-by-program basis.See the description of the programs resource, below.
installColormap (class Boolean)
On PseudoColor (8-bit) displays, install a private colormap while thescreensaver is active, so that the graphics hacks can get as manycolors as possible. This is the default. (This only applies when thescreen's default visual is being used, since non-default visuals gettheir own colormaps automatically.) This can also be overridden on aper-hack basis: see the discussion of the default-n name in thesection about the programs resource.

This does nothing if you have a TrueColor (16-bit or deeper) display.

verbose (class Boolean)
Whether to print diagnostics. Default false.
timestamp (class Boolean)
Whether to print the time of day along with any other diagnostic messages.Default true.
splash (class Boolean)
Whether to display a splash screen at startup. Default true.
splashDuration (class Time)
How long the splash screen should remain visible; default 5 seconds.
quad (class Boolean)
If true, then four screensavers will be run on each monitor.Use at your own risk!
helpURL (class URL)
The splash screen has a Help button on it. When you press it, it willdisplay the web page indicated here in your web browser.
loadURL (class LoadURL)
This is the shell command used to load a URL into your web browser.The default setting will load it into Mozilla/Netscape if it is alreadyrunning, otherwise, will launch a new browser looking at the helpURL.
demoCommand (class DemoCommand)
This is the shell command run when the Demo button on the splash windowis pressed. It defaults toxscreensaver-demo(1).
prefsCommand (class PrefsCommand)
This is the shell command run when the Prefs button on the splash windowis pressed. It defaults to xscreensaver-demo -prefs.
nice (class Nice)
The sub-processes created by xscreensaver will be ``niced'' to thislevel, so that they are given lower priority than other processes on thesystem, and don't increase the load unnecessarily. The default is 10.

(Higher numbers mean lower priority; see nice(1)for details.)

fade (class Boolean)
If this is true, then when the screensaver activates, the current contentsof the screen will fade to black instead of simply winking out. This onlyworks on certain systems. A fade will also be done when switching graphicshacks (when the cycle timer expires.) Default: true.
unfade (class Boolean)
If this is true, then when the screensaver deactivates, the original contentsof the screen will fade in from black instead of appearing immediately. Thisonly works on certain systems, and if fade is true as well.Default false.
fadeSeconds (class Time)
If fade is true, this is how long the fade will be in seconds (default 3 seconds.)
fadeTicks (class Integer)
If fade is true, this is how many times a second the colormap willbe changed to effect a fade. Higher numbers yield smoother fades, butmay make the fades take longer than the specified fadeSeconds ifyour server isn't fast enough to keep up. Default 20.
captureStderr (class Boolean)
Whether xscreensaver should redirect its stdout and stderr streams tothe window itself. Since its nature is to take over the screen, you would notnormally see error messages generated by xscreensaver or the sub-programs itruns; this resource will cause the output of all relevant programs to bedrawn on the screensaver window itself, as well as being written to thecontrolling terminal of the screensaver driver process. Default true.
ignoreUninstalledPrograms (class Boolean)
There may be programs in the list that are not installed on the system,yet are marked as "enabled." If this preference is true, then such programs will simply be ignored. If false, then a warning will be printedif an attempt is made to run the nonexistent program. Also, thexscreensaver-demo(1)program will suppress the non-existent programs from the list if thisis true. Default: false.
font (class Font)
The font used for the stdout/stderr text, if captureStderr is true.Default *-medium-r-*-140-*-m-* (a 14 point fixed-width font.)
mode (class Mode)
Controls the behavior of xscreensaver. Legal values are:
When blanking the screen, select a random display mode from among thosethat are enabled and applicable. This is the default.
When blanking the screen, only ever use one particular display mode (theone indicated by the selected setting.)
When blanking the screen, just go black: don't run any graphics hacks.
Don't ever blank the screen, and don't ever allow the monitor to power down.

selected (class Integer)
When mode is set to one, this is the one, indicated by itsindex in the programs list. You're crazy if you count them andset this number by hand: letxscreensaver-demo(1)do it for you!
programs (class Programs)
The graphics hacks which xscreensaver runs when the user is idle.The value of this resource is a multi-line string, one sh-syntaxcommand per line. Each line must contain exactly one command: nosemicolons, no ampersands.

When the screensaver starts up, one of these is selected (according tothe mode setting), and run. After the cycle periodexpires, it is killed, and another is selected and run.

If a line begins with a dash (-) then that particular program isdisabled: it won't be selected at random (though you can still selectit explicitly using thexscreensaver-demo(1)program.)

If all programs are disabled, then the screen will just be made blank,as when mode is set to blank.

To disable a program, you must mark it as disabled with a dash insteadof removing it from the list. This is because the system-wide (app-defaults)and per-user (.xscreensaver) settings are merged together, and if a userjust deletes an entry from their programs list, but that entry stillexists in the system-wide list, then it will come back. However, if theuser disables it, then their setting takes precedence.

If the display has multiple screens, then a different program will be runfor each screen. (All screens are blanked and unblanked simultaniously.)

Note that you must escape the newlines; here is an example of how youmight set this in your ~/.xscreensaver file:

programs:  \       qix -root                          \n\       ico -r -faces -sleep 1 -obj ico    \n\       xdaliclock -builtin2 -root         \n\       xv -root -rmode 5 image.gif -quit  \n

Make sure your $PATH environment variable is set up correctlybefore xscreensaver is launched, or it won't be able to find theprograms listed in the programs resource.

To use a program as a screensaver, two things are required: that thatprogram draw on the root window (or be able to be configured to draw onthe root window); and that that program understand ``virtual root''windows, as used by virtual window managers such astvtwm(1).(Generally, this is accomplished by just including the "vroot.h" header file in the program's source.)

If there are some programs that you want to run only when using a colordisplay, and others that you want to run only when using a monochromedisplay, you can specify that like this:

       mono:   mono-program  -root        \n\       color:  color-program -root        \n\

More generally, you can specify the kind of visual that should be used forthe window on which the program will be drawing. For example, if one program works best if it has a colormap, but another works best if it hasa 24-bit visual, both can be accommodated:

       PseudoColor: cmap-program  -root   \n\       TrueColor:   24bit-program -root   \n\

In addition to the symbolic visual names described above (in the discussionof the visualID resource) one other visual name is supported inthe programs list:
This is like default, but also requests the use of the default colormap,instead of a private colormap. (That is, it behaves as if the -no-install command-line option was specified, but only forthis particular hack.) This is provided because some third-party programsthat draw on the root window (notably: xv(1),andxearth(1))make assumptions about the visual and colormap of the root window: assumptions which xscreensaver can violate.

If you specify a particular visual for a program, and that visual does notexist on the screen, then that program will not be chosen to run. Thismeans that on displays with multiple screens of different depths, you canarrange for appropriate hacks to be run on each. For example, if one screenis color and the other is monochrome, hacks that look good in mono can be run on one, and hacks that only look good in color will show up on the other.

You shouldn't ever need to change the following resources:

pointerPollTime (class Time)
When server extensions are not in use, this controls how frequently xscreensaver checks to see if the mouse position or buttonshave changed. Default 5 seconds.
windowCreationTimeout (class Time)
When server extensions are not in use, this controls the delay between when windows are created and when xscreensaver selects events on them.Default 30 seconds.
initialDelay (class Time)
When server extensions are not in use, xscreensaver will wait this manyseconds before selecting events on existing windows, under the assumption that xscreensaver is started during your login procedure, and the window state may be in flux. Default 0. (This used to default to 30, but that wasback in the days when slow machines and X terminals were more common...)

There are a number of different X server extensions which can makexscreensaver's job easier. The next few resources specify whether theseextensions should be utilized if they are available.

sgiSaverExtension (class Boolean)
This resource controls whether the SGI SCREEN_SAVER server extensionwill be used to decide whether the user is idle. This is the default if xscreensaver has been compiled with support for this extension (which is the default on SGI systems.). If it is available, the SCREEN_SAVER method is faster and more reliable than what willbe done otherwise, so use it if you can. (This extension is only availableon Silicon Graphics systems, unfortunately.)
mitSaverExtension (class Boolean)
This resource controls whether the MIT-SCREEN-SAVER server extensionwill be used to decide whether the user is idle. However, the default forthis resource is false, because even if this extension is available,it is flaky (and it also makes the fade option not work properly.)Use of this extension is not recommended.
xidleExtension (class Boolean)
This resource controls whether the XIDLE server extension will beused to decide whether the user is idle. This is the default if xscreensaver has been compiled with support for this extension.(This extension is only available for X11R4 and X11R5 systems, unfortunately.)
procInterrupts (class Boolean)
This resource controls whether the /proc/interrupts file should beconsulted to decide whether the user is idle. This is the defaultif xscreensaver has been compiled on a system which supports thismechanism (i.e., Linux systems.)

The benefit to doing this is that xscreensaver can note that the useris active even when the X console is not the active one: if the user is typing in another virtual console, xscreensaver will notice that and willfail to activate. For example, if you're playing Quake in VGA-mode, xscreensaver won't wake up in the middle of your game and start competing for CPU.

The drawback to doing this is that perhaps you really do want idlenesson the X console to cause the X display to lock, even if there is activityon other virtual consoles. If you want that, then set this option to False.(Or just lock the X console manually.)

The default value for this resource is True, on systems where it works.

overlayStderr (class Boolean)
If captureStderr is True, and your server supports ``overlay'' visuals,then the text will be written into one of the higher layers instead of intothe same layer as the running screenhack. Set this to False to disable that (though you shouldn't need to.)
overlayTextForeground (class Foreground)
The foreground color used for the stdout/stderr text, if captureStderris true. Default: Yellow.
overlayTextBackground (class Background)
The background color used for the stdout/stderr text, if captureStderris true. Default: Black.
bourneShell (class BourneShell)
The pathname of the shell that xscreensaver uses to start subprocesses.This must be whatever your local variant of /bin/sh is: in particular,it must not be csh.


xscreensaveralso accepts a few command-line options, mostly for use when debugging:for normal operation, you should configure things via the ~/.xscreensaverfile.
-display host:display.screen
The X display to use. For displays with multiple screens, XScreenSaverwill manage all screens on the display simultaniously.
Same as setting the verbose resource to true: print diagnosticson stderr and on the xscreensaver window.
Same as setting the captureStderr resource to false: do notredirect the stdout and stderr streams to the xscreensaver window itself.If xscreensaver is crashing, you might need to do this in order to seethe error message.


When it is time to activate the screensaver, a full-screen black window iscreated on each screen of the display. Each window is created in such a waythat, to any subsequently-created programs, it will appear to be a ``virtualroot'' window. Because of this, any program which draws on the root window (and which understands virtual roots) can be used as a screensaver.

When the user becomes active again, the screensaver windows are unmapped, andthe running subprocesses are killed by sending them SIGTERM. This is also how the subprocesses are killed when the screensaver decides that it'stime to run a different demo: the old one is killed and a new one is launched.

Before launching a subprocess, xscreensaver stores an appropriate valuefor $DISPLAY in the environment that the child will receive. (This isso that if you start xscreensaver with a -display argument, theprograms which xscreensaver launches will draw on the same display;and so that the child will end up drawing on the appropriate screen of amulti-headed display.)

When the screensaver turns off, or is killed, care is taken to restore the ``real'' virtual root window if there is one. Because of this, it isimportant that you not kill the screensaver process with kill -9 ifyou are running a virtual-root window manager. If you kill it with -9,you may need to restart your window manager to repair the damage. Thisisn't an issue if you aren't running a virtual-root window manager.

For all the gory details, see the commentary at the top of xscreensaver.c.

You can control a running screensaver process by using thexscreensaver-command(1)program (which see.) 


Modern X servers contain support to power down the monitor after an idleperiod. If the monitor has powered down, then xscreensaver willnotice this (after a few minutes), and will not waste CPU by drawing graphics demos on a black screen. An attempt will also be made toexplicitly power the monitor back up as soon as user activity is detected.

As of version 3.28 (Feb 2001), the ~/.xscreensaver file controls theconfiguration of your display's power management settings: if you haveusedxset(1)to change your power management settings, then xscreensaver willoverride those changes with the values specified in ~/.xscreensaver (or with its built-in defaults, if thereis no ~/.xscreensaver file yet.)

To change your power management settings, runxscreensaver-demo(1)and change the various timeouts through the user interface.Alternately, you can edit the ~/.xscreensaver file directly.

If the power management section is grayed out in thexscreensaver-demo(1)window, then that means that your X server does not supportthe XDPMS extension, and so control over the monitor's power stateis not available.

If you're using a laptop, don't be surprised if changing the DPMSsettings has no effect: many laptops have monitor power-saving behaviorbuilt in at a very low level that is invisible to Unix and X. On suchsystems, you can typically adjust the power-saving delays only bychanging settings in the BIOS in some hardware-specific way.

If DPMS seems not to be working with XFree86, make sure the "DPMS"option is set in your /etc/X11/XF86Config file. See theXF86Config(5)manual for details. 


You can run xscreensaver from your xdm(1)session, so that the screensaver will run even when nobody is logged in on the console.

The trick to using xscreensaver with xdm is this: keep in mind the two very different states in which xscreensaver will be running:

1: Nobody logged in.

If you're thinking of running xscreensaver from XDM at all, then it's probably because you want graphics demos to be running on the consolewhen nobody is logged in there. In this case, xscreensaver will functiononly as a screen saver, not a screen locker: it doesn't make sensefor xscreensaver to lock the screen, since nobody is logged in yet!The only thing on the screen is the XDM login prompt.

2: Somebody logged in.

Once someone has logged in through the XDM login window, the situation isvery different. For example: now it makes sense to lock the screen (andprompt for the logged in user's password); and now xscreensaver shouldconsult that user's ~/.xscreensaver file; and so on.

The difference between these two states comes down to a question of,which user is the xscreensaver process running as? For the firststate, it doesn't matter. If you start xscreensaver in the usualXDM way, then xscreensaver will probably end up running as root, which is fine for the first case (the ``nobody logged in'' case.)

However, once someone is logged in, running as root is no longer fine:because xscreensaver will be consulting root's .xscreensaver fileinstead of that of the logged in user, and won't be prompting for thelogged in user's password, and so on. (This is not a security problem,it's just not what you want.)

So, once someone has logged in, you want xscreensaver to be running as thatuser. The way to accomplish this is to kill the old xscreensaver processand start a new one (as the new user.)

The simplest way to accomplish all of this is as follows:

1: Launch xscreensaver before anyone logs in.

To the file /usr/lib/X11/xdm/Xsetup, add the lines

xhost +localhostxscreensaver-command -exitxscreensaver &

This will run xscreensaver as root, over the XDM login window.Moving the mouse will cause the screen to un-blank, and allow the userto type their password at XDM to log in.

2: Restart xscreensaver when someone logs in.

Near the top of the file /usr/lib/X11/xdm/Xsession, add those same lines:

xscreensaver-command -exitxscreensaver &

When someone logs in, this will kill off the existing (root) xscreensaverprocess, and start a new one, running as the user who has just logged in.If the user's .xscreensaver file requests locking, they'll get it. Theywill also get their own choice of timeouts, and graphics demos, and so on.

Alternately, each user could just put those lines in their personal ~/.xsession files.

Make sure you have $PATH set up correctly in the Xsetup and Xsession scripts, or xdm won't be able to find xscreensaver, and/or xscreensaver won't be able to find its graphics demos.

(If your system does not seem to be executing the Xsetup file, youmay need to configure it to do so: the traditional way to do this isto make that file the value of the DisplayManager*setup resourcein the /usr/lib/X11/xdm/xdm-config file. See the man page forxdm(1)for more details.)

It is safe to run xscreensaver as root (as xdm is likely to do.) If run as root, xscreensaver changes its effective user and group ids to something safe (like "nobody") before connecting to the X serveror launching user-specified programs.

An unfortunate side effect of this (important) security precaution is thatit may conflict with cookie-based authentication.

If you get "connection refused" errors when running xscreensaverfrom xdm, then this probably means that you havexauth(1)or some other security mechanism turned on. One way around this is toadd "xhost +localhost" to Xsetup, just before xscreensaveris launched.

Note that this will give access to the X server to anyone capable of loggingin to the local machine, so in some environments, this might not be appropriate. If turning off file-system-based access control is notacceptable, then running xscreensaver from the Xsetup filemight not be possible, and xscreensaver will only work when running asa normal, unprivileged user.

For more information on the X server's access control mechanisms, see theman pages forX(1),Xsecurity(1),xauth(1),andxhost(1). 


Using xscreensaver withgdm(1)is easy, because gdm has a configuration tool. Just fire upgdmconfig(1)and on the Background page, type "xscreensaver -nosplash" intothe Background Program field. That will cause gdm to run xscreensaverwhile nobody is logged in, and kill it as soon as someone does log in.(The user will then be responsible for starting xscreensaver on theirown, if they want.)

Another way to accomplish the same thing is to edit thefile /etc/X11/gdm/gdm.conf to include:

BackgroundProgram=xscreensaver -nosplashRunBackgroundProgramAlways=true

In this situation, the xscreensaver process will probably be runningas user gdm instead of root. You can configure the settingsfor this nobody-logged-in state (timeouts, DPMS, etc.) by editingthe ~gdm/.xscreensaver file. 


I understand that KDE has invented their own wrapper around xscreensaver,that is inferior to xscreensaver-demo(1)in any number of ways. I've never actually seen it, but I'm told thatthis is the way you disable it:
1: Switch off KDE's screen saver.
Open the ``Control Center'' andselect the ``Look and Feel / Screensaver'' page.Turn off the ``Enable Screensaver'' checkbox.
2: Find your Autostart directory.
Open the ``Look and Feel / Desktop / Paths'' page,and see what your ``Autostart'' directory is set to: it willprobably be ~/.kde3/Autostart/ or something similar.
3: Make xscreensaver be an Autostart program.
Create a file in your autostart directory called xscreensaver.desktop that contains the following five lines:

[Desktop Entry]Exec=xscreensaverName=XScreensaverType=ApplicationX-KDE-StartupNotify=false

Now use xscreensaver normally, controlling it via the usualxscreensaver-demo(1)andxscreensaver-command(1)mechanisms. 


The easiest way to use xscreensaver on a system with CDE is to simplyswitch off the built-in CDE screensaver, and use xscreensaver instead;and second, to tell the front panel to run xscreensaver-command(1)with the -lock option when the Lock icon is clicked.

To accomplish this involves five steps:

1: Switch off CDE's locker
Do this by turning off ``Screen Saver and Screen Lock'' in theScreen section of the Style Manager.
2: Edit sessionetc
Edit the file ~/.dt/sessions/sessionetc and add to it the line

xscreensaver &

And make sure the sessionetc file is executable.This will cause xscreensaver to be launched when you log in.(As always, make sure that xscreensaver and the graphics demos are onyour $PATH; the path needs to be set in .cshrc and/or .dtprofile, not .login.)

3: Create XScreenSaver.dt
Create a file called ~/.dt/types/XScreenSaver.dt with the followingcontents:

ACTION XScreenSaver{  LABEL         XScreenSaver  TYPE          COMMAND  EXEC_STRING   xscreensaver-command -lock  ICON          Dtkey  WINDOW_TYPE   NO_STDIO}

This defines a ``lock'' command for the CDE front panel, that knows howto talk to xscreensaver.

4: Create Lock.fp
Create a file called ~/.dt/types/Lock.fp with the followingcontents:

CONTROL Lock{  TYPE             icon  CONTAINER_NAME   Switch  CONTAINER_TYPE   SWITCH  POSITION_HINTS   1  ICON             Fplock  LABEL            Lock  PUSH_ACTION      XScreenSaver  HELP_TOPIC       FPOnItemLock  HELP_VOLUME      FPanel}

This associates the CDE front panel ``Lock'' icon with the lock commandwe just defined in step 3.

5: Restart
Select ``Restart Workspace Manager'' from the popup menu to makeyour changes take effect. If things seem not to be working, check thefile ~/.dt/errorlog for error messages.


Since CDE is a descendant of VUE, the instructions for using xscreensaverunder VUE are similar to the above:
1: Switch off VUE's locker
Open the ``Style Manager'' and select ``Screen.''Turn off ``Screen Saver and Screen Lock'' option.
2: Make sure you have a Session
Next, go to the Style Manager's, ``Startup'' page.Click on ``Set Home Session'' to create a session, then on ``Return to Home Session'' to select this session eachtime you log in.
3: Edit vue.session
Edit the file ~/.vue/sessions/home/vue.session and add to itthe line

vuesmcmd -screen 0 -cmd "xscreensaver"

This will cause xscreensaver to be launched when you log in.(As always, make sure that xscreensaver and the graphics demos are onyour $PATH; the path needs to be set in .cshrcand/or .profile, not .login.)

3: Edit vuewmrc
Edit the file ~/.vue/vuewmrc and add (or change) the Lock control:

CONTROL Lock{  TYPE         button  IMAGE        lock  PUSH_ACTION  f.exec "xscreensaver-command -lock"  HELP_TOPIC   FPLock}

This associates the VUE front panel ``Lock'' icon with the xscreensaver lock command.



Bugs? There are no bugs. Ok, well, maybe. If you find one, please letme know. explains how toconstruct the most useful bug reports.
Locking and XDM
If xscreensaver has been launched from xdm(1)before anyone has logged in, you will need to kill and then restart thexscreensaver daemon after you have logged in, or you will be confused bythe results. (For example, locking won't work, and your ~/.xscreensaverfile will be ignored.)

When you are logged in, you want the xscreensaver daemon to be running under your user id, not as root or some other user.

If it has already been started by xdm, you can kill it by sendingit the exit command, and then re-launching it as you, by puttingsomething like the following in your personal X startup script:

xscreensaver-command -exitxscreensaver &

The ``Using XDM(1)'' section, above, goes into more detail, and explainshow to configure the system to do this for all users automatically.

Locking and root logins
In order for it to be safe for xscreensaver to be launched by xdm,certain precautions had to be taken, among them that xscreensaver neverruns as root. In particular, if it is launched as root (as xdmis likely to do), xscreensaver will disavow its privileges, and switch itself to a safe user id (such as nobody.)

An implication of this is that if you log in as root on the console, xscreensaver will refuse to lock the screen (because it can't tellthe difference between root being logged in on the console, and anormal user being logged in on the console but xscreensaver having been launched by thexdm(1)Xsetupfile.)

The solution to this is simple: you shouldn't be logging in on the consoleas root in the first place! (What, are you crazy or something?)

Proper Unix hygiene dictates that you should log in as yourself, andsu(1)to root as necessary. People who spend their day logged inas root are just begging for disaster.

For xscreensaver to work when launched byxdm(1),programs running on the local machine as user "nobody" must beable to connect to the X server. This means that if you want to runxscreensaver on the console while nobody is logged in, you may needto disable cookie-based access control (and allow all users who can login to the local machine to connect to the display.)

You should be sure that this is an acceptable thing to do in yourenvironment before doing it. See the ``Using XDM(1)'' section, above, for more details.

If you get an error message at startup like ``couldn't get passwordof user'' then this probably means that you're on a system in which thegetpwent(3)library routine can only be effectively used by root. If this is the case, then xscreensaver must be installed as setuid to root in order forlocking to work. Care has been taken to make this a safe thing to do.

It also may mean that your system uses shadow passwords instead of the standardgetpwent(3)interface; in that case, you may need to change some options with configure and recompile.

If you change your password after xscreensaver has been launched, it willcontinue using your old password to unlock the screen until xscreensaveris restarted. On some systems, it may accept both your old and newpasswords. So, after you change your password, you'll have to do

xscreensaver-command -restart

to make xscreensaver notice.

PAM Passwords
If your system uses PAM (Pluggable Authentication Modules), then in orderfor xscreensaver to use PAM properly, PAM must be told about xscreensaver.The xscreensaver installation process should update the PAM data (on Linux,by creating the file /etc/pam.d/xscreensaver for you, and on Solaris, by telling you what lines to add to the /etc/pam.conf file.)

If the PAM configuration files do not know about xscreensaver, then you might be in a situation where xscreensaver will refuse to everunlock the screen.

This is a design flaw in PAM (there is no way for a client to tell thedifference between PAM responding ``I have never heard of your module,''and responding, ``you typed the wrong password.'') As far as I can tell,there is no way for xscreensaver to automatically work around this, ordetect the problem in advance, so if you have PAM, make sure it isconfigured correctly!

Colormap lossage: TWM
The installColormap option doesn't work very well with thetwm(1)window manager and its descendants, on 8-bit screens.

There is a race condition between the screensaver and this window manager,which can result in the screensaver's colormap not getting installedproperly, meaning the graphics hacks will appear in essentially randomcolors. (If the screen goes white instead of black, this is probably why.)

Themwm(1)andolwm(1)window managers don't have this problem. The race condition existsbecause X (really, ICCCM) does not provide a way for an OverrideRedirect window to have its own colormap, short of grabbing the server (which is neither a good idea, nor really possible with the current design.) What happens is that, as soon as xscreensaver installs its colormap, twm responds to the resultant ColormapNotify event by re-instaling the default colormap. Apparently, twm doesn't always do this; it seems to do it regularly if the screensaver is activated from a menu item, but seems to not do it if the screensaver comes on of its own volition, or is activated from another console.

Attention, window manager authors!
You should only callXInstallColormap(3)in response to user events. That is, it is appropriate to install a colormapin response to FocusIn, FocusOut, EnterNotify, and LeaveNotify events; but it is not appropriate to call it inresponse to ColormapNotify events. If you install colormaps inresponse to application actions as well as in response to useractions, then you create the situation where it is impossible for override-redirect applications (such as xscreensaver) to display theirwindows in the proper colors.
Colormap lossage: XV, XAnim, XEarth
Some programs don't operate properly on visuals other than the default one,or with colormaps other than the default one. See the discussion of themagic "default-n" visual name in the description of the programs resource in the Configuration section. When programs only work withthe default colormap, you need to use a syntax like this:

   default-n: xv -root image-1.gif -quit  \n\   default-n: xearth -nostars -wait 0     \n\

It would also work to turn off the installColormap option altogether,but that would deny extra colors to those programs that can takeadvantage of them.

Machine Load
Although this program ``nices'' the subprocesses that it starts, graphics-intensive subprograms can still overload the machine by causingthe X server process itself (which is not ``niced'') to consume manycycles. Care has been taken in all the modules shipped with xscreensaverto sleep periodically, and not run full tilt, so as not to causeappreciable load.

However, if you are running the OpenGL-based screen savers on a machinethat does not have a video card with 3D acceleration, they willmake your machine slow, despitenice(1).

Your options are: don't use the OpenGL display modes; or, collect thespare change hidden under the cushions of your couch, and use it tobuy a video card manufactured after 1998. (It doesn't even need to befast 3D hardware: the problem will be fixed if there is any3D hardware at all.)

XFree86's Magic Keystrokes
The XFree86 X server traps certain magic keystrokes before client programs eversee them. Two that are of note are Ctrl+Alt+Backspace, which causes the X server to exit; and Ctrl+Alt+Fn, which switches virtual consoles.The X server will respond to these keystrokes even if xscreensaver has thescreen locked. Depending on your setup, you might consider this a problem.

Unfortunately, there is no way for xscreensaver itself to override theinterpretation of these keys. If you want to disable Ctrl+Alt+Backspaceglobally, you need to set the DontZap flag in your /etc/X11/XF86Config file. To globally disable VT switching,you can set the DontVTSwitch flag. See theXF86Config(5)manual for details.

MIT Extension and Fading
The MIT-SCREEN-SAVER extension is junk. Don't use it.

When using the MIT-SCREEN-SAVER extension in conjunction with the fade option, you'll notice an unattractive flicker just before the fade begins. This is because the server maps a black window just before it tells the xscreensaver process to activate. The xscreensaver process immediately unmaps that window, but this results in a flicker. I haven't figured a way to get around this; it seems to be a fundamentalproperty of the (mis-) design of this server extension.

It sure would be nice if someone would implement the SGI SCREEN_SAVERextension in XFree86; it's dead simple, and works far better than theoverengineered and broken MIT-SCREEN-SAVER extension.

Keyboard LEDs
If procInterrupts is on (which is the default on Linux systems) andyou're using some program that toggles the state of your keyboard LEDs,xscreensaver won't work right: turning those LEDs on or off causes a keyboard interrupt, which xscreensaver will interpret as user activity.So if you're using such a program, set the procInterrupts resourceto False.
If you are not making use of one of the server extensions (XIDLE,SGI SCREEN_SAVER, or MIT-SCREEN-SAVER), then it is possible, in rare situations, for xscreensaver to interfere with event propagation and make another X program malfunction. For this to occur, that otherapplication would need to not select KeyPress events on its non-leaf windows within the first 30 seconds of their existence, but then select for them later. In this case, that client might fail to receive those events. This isn't very likely, since programs generally select aconstant set of events immediately after creating their windows and then don't change them, but this is the reason that it's a good idea to install and use one of the server extensions instead, to work around this shortcomingin the X protocol.

In all these years, I've not heard of even a single case of this happening,but it is theoretically possible, so I'm mentioning it for completeness...



to get the default host and display number, and to inform the sub-programsof the screen on which to draw.
to find the sub-programs to run.
for the directory in which to read the .xscreensaver file.
to get the name of a resource file that overrides the global resourcesstored in the RESOURCE_MANAGER property.


The latest version of xscreensaver, an online version of this manual,and a FAQ can always be found at 




Copyright © 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,2000, 2001, 2002, 2003, 2004 by Jamie Zawinski. Permission to use, copy,modify, distribute, and sell this software and its documentation forany purpose is hereby granted without fee, provided that the abovecopyright notice appear in all copies and that both that copyrightnotice and this permission notice appear in supporting documentation.No representations are made about the suitability of this software forany purpose. It is provided "as is" without express or impliedwarranty. 


Jamie Zawinski <>. Written in late 1991; version 1.0 postedto comp.sources.x on 17-Aug-1992.

Please let me know if you find any bugs or make any improvements. 


Thanks to Angela Goodman for the XScreenSaver logo.

Thanks to the many people who have contributed graphics demos to the package.

Thanks to David