To get gdm to run the BackgroundProgram, you may need to switch it from the "Graphical Greeter" to the "Standard Greeter". This nobody-logged-in state (timeouts, DPMS, etc.) by editing the ~gdm/.xscreensaver file. RunBackgroundProgramAlways=trueIn this situation, the xscreensaver process will probably be running as user gdm instead of root. Xscreensaver on their own, if they want.)Īnother way to accomplish the same thing is to edit the file /etc/X11/gdm/gdm.conf to include: (The user will then be responsible for starting That willĬause gdm to run xscreensaver while nobody is logged in, and kill it as soon as someone does log in. Run gdmconfig(1) and on the Background page, type the command "xscreensaver -nosplash" into the Background Program field. You can run xscreensaver from your gdm(1) session, so that the screensaver will run even when nobody is logged in on the console. Now use xscreensaver normally, controlling it via the usual xscreensaver-demo(1) and xscreensaver-command(1) mechanisms. Xscreensaver-command -lockMake sure the file is executable (chmod a+x). Possibly in /usr/lib/kde4/libexec/ or /usr/libexec/kde4/, depending on the distro and phase of the moon) with these two lines: Replace the file kdesktop_lock or krunner_lock or kscreenlocker in /usr/bin/ (or possibly in /usr/kde/3.5/bin/ or X-KDE-StartupNotify=false 4: Make the various "lock session" buttons call xscreensaver.
desktop file in your autostart directory called sktop that contains the following five lines: Xrdb Paths'' page, and see what your ''Autostart path'' is set to: it will probably be ~/.kde/Autostart/ orģ: Make xscreensaver be an Autostart program. Xdefaults file, and then tell the running xscreensaver process to restart itself, like so: If you change a setting in your X resource database, or if you want xscreensaver to notice your changes immediately instead of the next time it wakes up, Reloaded the next time the screen saver needs to take some action, such as blanking or unblanking the screen, or picking a new graphics mode.) xscreensaver file while xscreensaver is already running, it will notice this, and reload the file. Xscreensaver.timeout: 5If you change a setting in the. xscreensaver file, you would write the following: Xdefaults file for example, to set the timeout paramter in the xscreensaver file is similar to that of the. xscreensaver file exists, it overrides any settings in the resource database. xscreensaver file in your home directory or in the X resource database. Options to xscreensaver are stored in one of two places: in a.
XSCREENSAVER NOSPLASH MANUAL
This manual unless you are trying to do something tricky, like customize xscreensaver for site-wide use or something. You shouldn't need to know any of the stuff described in The easy way to configure xscreensaver is to run the xscreensaver-demo(1) program. Of this manual page describes lower level ways of changing settings.
The easiest way to configure xscreensaver is to simply run the xscreensaver-demo(1) program, and change the settings through the GUI. Note that xscreensaver has a client-server model: the xscreensaver program is a daemon that runs in the background it is controlled by theįoreground xscreensaver-demo(1) and xscreensaver-command(1) programs. Xscreensaver-demoThe xscreensaver-demo(1) program pops up a dialog box that lets you configure the screen saver, and experiment with the various display modes. It also provides configuration and control of your monitor's power-saving features. 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 on It turns offĪs soon as there is any mouse or keyboard activity. The xscreensaver program waits until the keyboard and mouse have been idle for a period, and then runs a graphics demo chosen at random.
XSCREENSAVER NOSPLASH PLUS
Xscreensaver - extensible screen saver framework, plus locking
0 kommentar(er)
