.if n .sp 1
.if t .sp .5
..
-.TH XScreenSaver 1 "02-Jan-2002 (4.00)" "X Version 11"
+.TH XScreenSaver 1 "03-Feb-2003 (4.07)" "X Version 11"
.SH NAME
xscreensaver - extensible screen saver framework, plus locking
.SH SYNOPSIS
drawn on the screensaver window itself, as well as being written to the
controlling terminal of the screensaver driver process. Default true.
.TP 8
+.B ignoreUninstalledPrograms\fP (class \fBBoolean\fP)
+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 printed
+if an attempt is made to run the nonexistent program. Also, the
+.BR xscreensaver-demo (1)
+program will suppress the non-existent programs from the list if this
+is true. Default: false.
+.TP 8
.B font\fP (class \fBFont\fP)
The font used for the stdout/stderr text, if \fBcaptureStderr\fP is true.
Default \fB*\-medium\-r\-*\-140\-*\-m\-*\fP (a 14 point fixed-width font.)
built in at a very low level that is invisible to Unix and X. On such
systems, you can typically adjust the power-saving delays only by
changing 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 \fI/etc/X11/XF86Config\fP file. See the
+.BR XF86Config (5)
+manual for details.
.SH USING XDM(1)
You can run \fIxscreensaver\fP from your
.BR xdm (1)
and
.BR xhost (1).
.SH USING GDM(1)
-The instructions for using \fIxscreensaver\fP with
+Using xscreensaver with
.BR gdm (1)
-are almost the same as for using
-.BR xdm (1),
-above. There are only two differences, really: instead
-of editing \fI/usr/lib/X11/xdm/Xsetup\fP, edit the
-file \fI/etc/X11/gdm/Init/Default\fP; and instead of
-editing \fI/usr/lib/X11/xdm/Xsession\fP, edit one or all of the
-files in the \fI/etc/X11/gdm/Sessions/\fP directory. (Note that
-the default session (\fI/etc/X11/gdm/Sessions/Default\fP) usually
-simply executes \fI/usr/lib/X11/xdm/Xsession\fP, so be careful
-you aren't initializing xscreensaver twice.)
-
-All the same caveats apply for
-.BR gdm (1)
-as for
-.BR xdm (1).
+is easy, because gdm has a configuration tool. Just fire up
+.BR gdmconfig (1)
+and on the \fIBackground\fP page, type \fB"xscreensaver -nosplash"\fP into
+the \fIBackground Program\fP field. That will cause gdm to run xscreensaver
+while nobody is logged in, and kill it as soon as someone does log in.
+(The user will then be responsible for starting xscreensaver on their
+own, if they want.)
+
+In this situation, the \fIxscreensaver\fP process will probably be running
+as user \fIgdm\fP instead of \fIroot\fP. You can configure the settings
+for this nobody-logged-in state (timeouts, DPMS, etc.) by editing
+the \fI~gdm/.xscreensaver\fP file.
.SH USING CDE (COMMON DESKTOP ENVIRONMENT)
The easiest way to use \fIxscreensaver\fP on a system with CDE is to simply
switch off the built-in CDE screensaver, and use \fIxscreensaver\fP instead;
lock command.
.RE
.PP
+.SH USING KDE (K DESKTOP ENVIRONMENT)
+I understand that KDE has invented their own wrapper around xscreensaver,
+that is inferior to
+.BR xscreensaver-demo (1)
+in any number of ways. I've never actually seen it, but I'm told that
+this is the way you disable it:
+.RS 4
+.TP 3
+\fB1: Switch off KDE's screen saver.\fP
+Open the ``\fIControl Center\fP'' and
+select the ``\fILook and Feel / Screensaver\fP'' page.
+Turn off the ``\fIEnable Screensaver\fP'' checkbox.
+.TP 3
+\fB2: Find your Autostart directory.\fP
+Open the ``\fILook and Feel / Desktop / Paths\fP'' page,
+and see what your ``Autostart'' directory is set to: it will
+probably be \fI~/.kde3/Autostart/\fP or something similar.
+.TP 3
+\fB3: Make xscreensaver be an Autostart program.\fP
+Create a file in your autostart directory
+called \fIxscreensaver.desktop\fP that contains the following five lines:
+.EX
+[Desktop Entry]
+Exec=xscreensaver
+Name=XScreensaver
+Type=Application
+X-KDE-StartupNotify=false
+.EE
+.RE
+.PP
+Now use xscreensaver normally, controlling it via the usual
+.BR xscreensaver-demo (1)
+and
+.BR xscreensaver-command (1)
+mechanisms.
.SH ADDING TO MENUS
The
.BR xscreensaver-command (1)
Unfortunately, there is no way for xscreensaver itself to override the
interpretation of these keys. If you want to disable Ctrl+Alt+Backspace
globally, you need to set the \fIDontZap\fP flag in
-your \fI/etc/X11/XF86Config\fP file. See the
+your \fI/etc/X11/XF86Config\fP file. To globally disable VT switching,
+you can set the \fIDontVTSwitch\fP flag. See the
.BR XF86Config (5)
manual for details.
-There is no way (as far as I can tell) to disable the VT-switching keystrokes.
-
Some Linux systems come with a VT_LOCKSWITCH ioctl, that one could
theoretically use to prevent VT-switching while the screen is locked;
but unfortunately, this ioctl can only be used by root, which means
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...
-.TP 8
-.B Red Hot Lava
-There need to be a lot more graphics hacks. In particular, there should be
-a simulation of a Lavalite (tm).
.SH ENVIRONMENT
.PP
.TP 8
projects / xscreensaver / blobdiff