![]() ![]() This is the same as running xscreensaver-command(1) with the -exit Kill Daemon If the xscreensaver daemon is running on this screen, kill it. Running xscreensaver-command(1) with the -lock option. Lock Screen Now Just like Blank Screen Now, except the screen will be locked as well (even if it is not configured to lock all the time.) This is the same as Xscreensaver-command(1) with the -activate option. The first page is for editing the list of demos, and the second is for editing various otherĪll of these commands are on either the File or Help menus:īlank Screen Now Activates the background xscreensaver daemon, which will then run a demo at random. The main window consists of a menu bar and two tabbed pages. It is essentially two things: a tool for editing the ~/.xscreensaver file and a tool forĭemoing the various graphics hacks that the xscreensaver daemon will launch. Go to Applications → Settings → Power Manager menu.The xscreensaver-demo program is a graphical front-end for setting the parameters usedīy the background xscreensaver(1) daemon. We apply that to the situation of closing the laptop lid, the system goes to sleep and the screen is locked by XScreenSaver, in XFCE. The password dialog will pop up for the user to unlock. When the system wakes up, the screensaver is deactivated as if there's user activity. No demo program is run and the screen is turned off. However, Lock Screen After is ignored and the screen is locked immediately. At this point the screensaver is activated as if the user has not touched the mouse or keyboard until Blank After. Using XScreenSaver in conjunction with the desktop environment's Power Manager program Because we have xscreensaver-systemd, before the system goes to sleep it immediately locks the screen. However, this can be easily overcome by increasing the service's waiting time to restart, for example RestartSec=3min. ![]() If you run xscreensaver from the systemd service, in case you set Blank After to be too small, the screensaver will be activated too soon, leading to the creation of the root window and drawing operation of the demo program may fail. If you run xscreensaver from the desktop file, the desktop environment is ready to run it at the appropriate time. So how is the "safety" different? The difference is mostly at startup time (when logging into the desktop environment). If you want to control xscreensaver running, stopping, even disabling automatic startup without affecting other users, and want screensaver and screen locking activities to be performed exactly, use the systemd service. If you are not interested in controlling how xscreensaver operates and want it to run safely during a desktop environment session, use the desktop file. rvice or sktop? Which one to use depends on your preference. ![]() Therefore you need to install it manually, as a root user: cp driver/xscreensaver-systemd /usr/bin/Ĥ) Creating user service You create the xscreensaver service as follows, as the root user: cat > /usr/lib/systemd/user/rvice /etc/xdg/autostart/sktop << "EOF" Type=Application Name=Screensaver Comment=Launch screensaver and locker program Icon=preferences-desktop-screensaver Exec=xscreensaver -no-splash TryExec=xscreensaver OnlyShowIn=KDE GNOME XFCE X-GNOME-Autostart-Notify=false X-KDE-StartupNotify=false EOF However, the default installation does not copy this program file. The package has been configured using the libsystemd library and the compilation process creates an xscreensaver-systemd helper program. configure -prefix=/usr -with-systemdģ) Installing Run the following installation command, as the root user: make install If you want to build the package yourself, follow the instructions below: 1) Package configuration. However, building it needs a little meticulous so as not to cause conflict in the system when the screensaver activates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |