I am using Fedora 25 with Wayland and GNOME. How can I configure a screensaver? I assume xscreensaver does not work and I could install gnome-screensaver, but there is no configuration interface - or have I missed something there…? **Edit**: To clarify, I am not looking for a simple black screen or a "fade out" effect, but for a "real" screensaver showing some animation or a slideshow of your photos/images or so… ----- Question cross-posted from [Ask Fedora](https://ask.fedoraproject.org/en/question/106077/how-can-i-activateconfigure-a-screensaver-in-waylandgnome/) .

I am running Linux Mint 17.1, Cinnamon Desktop, Compiz, and XScreenSaver. I want to be able to use the Desktop Lock Screen and turn off the XScreenSaver Lock Screen. Turning off the Lock Screen in the XScreenSaver GUI deactivates all Screen Locking.

At some point last month, I realized my screensaver (xscreensaver in this case) was no longer blanking the screen (and therefore also not locking it, and going into dpms idle/standby) at all. I had not changed any settings, but I did install nomachine in that time, which I suspected might be the culprit, but the nomachine server was disabled and that did not make a difference. Strangely, even when I manually locked the screen, after a few seconds of the screen being locked, it would prompt for my password to unlock, as if the mouse had been moved, and therefore dpms/standby never had a chance to kick in. But checking my mouse, and putting it on its side, and running xinput diagnostics eliminated hardware issues as the reason. Other questions ask similar things, but I figured I would create this question to compile what I did to solve my problem, in the hopes that it will help someone else. In other forums/questions, it is mentioned that this affects other things like hibernation and sleep, so hopefully this will give others a chance at solving this if they run into it in their use cases.

I'm using an old **Gateway NE56R Notebook** with a fresh new **Debian 12.7 LXDE** and trying to set the **screen-saver** to **turn-off the display after 1 minute of user inactivity.** For that, I've set the following at the screen-saver gui (XScreenSaver Settings): - Blank Screen Only Mode - Blank After 1 minute - Cycle After 0 minute - Power-Management Disabled (ie: box uncheck) - Quick Power-Off in Blank Only Mode Unfortunately, it did not work. After 1 minute the screen turned blank but the display was still on (ie: **backlight on**). I have already tried several other settings, including via xset, and switching xscreensaver daemon on/off, but neither worked. Briefly: - The display doesn't turn-off (ie: blank screen but backlight still on); OR - If the display turns off, the whole system randomly reboot/turn-off after a while (somewhere between 0~1000 seconds). ### Question ### How to set the screen-saver to turn-off the display after XX minutes ??? What am I missing? What is going on? Ideas? ----------------------------------------------------- ### Debug Examples ### ##### Example 1 (xscreensaver daemon ON, AC power): #####

root@debian:~# xset q
[...]
Screen Saver:
  prefer blanking:  no    allow exposures:  no
  timeout:  0    cycle:  0
[...]
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On
root@debian:~# xset dpms force off

Display turns-off then notebook reboot. ##### Example 2 (xscreensaver daemon ON, battery): #####

root@debian:~# xset q
[...]
Screen Saver:
  prefer blanking:  no    allow exposures:  no
  timeout:  0    cycle:  0
[...]
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On
root@debian:~# xset dpms force off

Display turns-off then notebook turns-off. ##### Example 3 (xscreensaver daemon OFF, AC power): #####

root@debian:~# xset q
[...]
Screen Saver:
  prefer blanking:  no    allow exposures:  no
  timeout:  0    cycle:  0
[...]
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 60
  DPMS is Disabled
root@debian:~# xset dpms force off

Display turns-off then notebook reboot after 250 seconds.

I have installed the rss-glx package in my Suse Tumbleweed system, and I can see the binaries in /usr/bin/ (the binaries work flawlessly), the symbolic links from /usr/lib64/xscreensaver/ to the binaries, and the corresponding XML files in /etc/xscreensaver/. What I don't see are the new hacks in the list provided to me by xscreensaver-demo! Here it is one of those XML files $ cat /etc/xscreensaver/pixelcity.xml Procedural city fly through. Written by Shamus Young . Ported to Linux by Tugrul Galatali - . and the associated paths in the binaries directories /usr/bin/rss-glx-pixelcity /usr/lib64/xscreensaver/rss-glx-pixelcity I can see two issues, 1. no reference to the actual binary name in the XML file 2. the symbolic links to rss-glx binaries are in /usr/lib64/xscreensaver/ but XScreensaver binaries are in a different place, /usr/libexec/xscreensaver/. I don't know what to do, what should I do?

I use a vnc (tightvncserver) connection: Devuan/aarch64 and Armbian(Debian)/armfh (hosts) thru Win10/TigerVNC (client). Since the upgrade of the underlying base to Debian Bookworm, xscreensaver and any other locker fail to run for the same reason:

xscreensaver --no-splash
xscreensaver: 12:09:54: XInput extension missing

xtrlock -f
xtrlock (version 2.15): No X Input extension

I reached out the **Xscreensaver** developer, and he told me the Debian package brings with it all the necessary dependencies, and he doesn't know where the problem is. I also installed a bunch of additional packages but nothing has changed:

libx11-xcb1/stable-security,now 2:1.8.4-2+deb12u2 arm64 [installed,automatic]
libxcb-damage0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-dri2-0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-dri3-0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-glx0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-icccm4/stable,now 0.4.1-1.1 arm64 [installed,automatic]
libxcb-image0/stable,now 0.4.0-2 arm64 [installed,automatic]
libxcb-keysyms1/stable,now 0.4.0-1+b2 arm64 [installed,automatic]
libxcb-present0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-randr0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-render-util0/stable,now 0.3.9-1+b1 arm64 [installed,automatic]
libxcb-render0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-screensaver0/stable,now 1.15-1 arm64 [installed]
libxcb-shape0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-shm0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-sync1/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-util1/stable,now 0.4.0-1+b1 arm64 [installed,automatic]
libxcb-xfixes0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xinerama0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xinput0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xkb1/stable,now 1.15-1 arm64 [installed,automatic]
libxcb1-dev/stable,now 1.15-1 arm64 [installed,automatic]
libxcb1/stable,now 1.15-1 arm64 [installed,automatic]

On Bullseye, xscreensaver and other lockers were working just fine, I can't figure out how to fix this, thanks!

Wanting to run a video as my screensaver, I ran into problems configuring it appropriately. I am summarizing the solution here in Q&A format.

Upon running sudo apt remove xscreensaver I am prompted with the below messages. Is this normal? Should I proceed? Why would removing a screensaver involve so many things? I'm using LXDE desktop, by the way, can I safely remove lubuntu-desktop? The following additional packages will be installed: accountsservice-ubuntu-schemas activity-log-manager apg aptdaemon-data cheese-common dconf-cli evolution-data-server evolution-data-server-common gir1.2-dbusmenu-glib-0.4 gir1.2-ibus-1.0 gir1.2-vte-2.91 gkbd-capplet gnome-bluetooth gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-online-accounts gnome-power-manager gnome-screensaver gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-startup-applications gnome-user-docs gsettings-ubuntu-schemas gstreamer1.0-clutter-3.0 ibus ibus-data ibus-gtk ibus-gtk3 indicator-applet indicator-application indicator-appmenu indicator-bluetooth indicator-common indicator-datetime indicator-keyboard indicator-messages indicator-power indicator-printers indicator-session indicator-sound jayatana language-selector-gnome libaccounts-glib0 libbamf3-2 libcamel-1.2-62 libcanberra-pulse libcheese-gtk25 libcheese8 libclutter-1.0-0 libclutter-1.0-common libclutter-gst-3.0-0 libclutter-gtk-1.0-0 libcogl-common libcogl-pango20 libcogl-path20 libcogl20 libcolord-gtk1 libdee-1.0-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgeonames-common libgeonames0 libgnome-bluetooth13 libgnome-panel0 libgnomekbd-common libgnomekbd8 libgoa-backend-1.0-1 libgsound0 libgssdp-1.2-0 libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libibus-1.0-5 libido3-0.1-0 libindicator3-7 liblightdm-gobject-1-0 libmediaart-2.0-0 libmessaging-menu0 libphonenumber7 libprotobuf17 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libtimezonemap-data libtimezonemap1 libunity-control-center1 libunity-gtk2-parser0 libunity-gtk3-parser0 libunity-settings-daemon1 liburl-dispatcher1 libwhoopsie-preferences0 libxklavier16 libzeitgeist-2.0-0 light-locker light-locker-settings lightdm mousetweaks nautilus-data python3-aptdaemon.gtk3widgets python3-ibus-1.0 python3-macaroonbakery python3-protobuf python3-psutil python3-rfc3339 python3-tz rygel session-migration ubuntu-docs ubuntu-system-service ubuntu-touch-sounds unity-control-center unity-greeter unity-gtk-module-common unity-gtk2-module unity-gtk3-module unity-settings-daemon unity-settings-daemon-schemas whoopsie-preferences zeitgeist-core Suggested packages: evolution gnome-software | gnome-packagekit gnome-user-share realmd libcanberra-gtk-module usbguard ibus-clutter ibus-doc unity-greeter-session-broadcast url-dispatcher bindfs python-psutil-doc gstreamer1.0-libav gstreamer1.0-plugins-ugly rygel-playbin rygel-preferences rygel-ruih rygel-tracker tumbler zeitgeist-datahub Recommended packages: appmenu-qt systemd-services The following packages will be REMOVED: lubuntu-desktop xscreensaver The following NEW packages will be installed: accountsservice-ubuntu-schemas activity-log-manager apg aptdaemon-data cheese-common dconf-cli evolution-data-server evolution-data-server-common gir1.2-dbusmenu-glib-0.4 gir1.2-ibus-1.0 gir1.2-vte-2.91 gkbd-capplet gnome-bluetooth gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-online-accounts gnome-power-manager gnome-screensaver gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-startup-applications gnome-user-docs gsettings-ubuntu-schemas gstreamer1.0-clutter-3.0 ibus ibus-data ibus-gtk ibus-gtk3 indicator-applet indicator-application indicator-appmenu indicator-bluetooth indicator-common indicator-datetime indicator-keyboard indicator-messages indicator-power indicator-printers indicator-session indicator-sound jayatana language-selector-gnome libaccounts-glib0 libbamf3-2 libcamel-1.2-62 libcanberra-pulse libcheese-gtk25 libcheese8 libclutter-1.0-0 libclutter-1.0-common libclutter-gst-3.0-0 libclutter-gtk-1.0-0 libcogl-common libcogl-pango20 libcogl-path20 libcogl20 libcolord-gtk1 libdee-1.0-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgeonames-common libgeonames0 libgnome-bluetooth13 libgnome-panel0 libgnomekbd-common libgnomekbd8 libgoa-backend-1.0-1 libgsound0 libgssdp-1.2-0 libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libibus-1.0-5 libido3-0.1-0 libindicator3-7 liblightdm-gobject-1-0 libmediaart-2.0-0 libmessaging-menu0 libphonenumber7 libprotobuf17 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libtimezonemap-data libtimezonemap1 libunity-control-center1 libunity-gtk2-parser0 libunity-gtk3-parser0 libunity-settings-daemon1 liburl-dispatcher1 libwhoopsie-preferences0 libxklavier16 libzeitgeist-2.0-0 light-locker light-locker-settings lightdm mousetweaks nautilus-data python3-aptdaemon.gtk3widgets python3-ibus-1.0 python3-macaroonbakery python3-protobuf python3-psutil python3-rfc3339 python3-tz rygel session-migration ubuntu-docs ubuntu-system-service ubuntu-touch-sounds unity-control-center unity-greeter unity-gtk-module-common unity-gtk2-module unity-gtk3-module unity-settings-daemon unity-settings-daemon-schemas whoopsie-preferences zeitgeist-core 0 upgraded, 136 newly installed, 2 to remove and 0 not upgraded. Need to get 40.3 MB of archives. After this operation, 144 MB of additional disk space will be used. Do you want to continue? [Y/n] n

I had the following setup: - For my screensaver, I used xscreensaver (because it's beautiful) - To lock my screen, I used light-locker (because it's more secure then xscreensaver) Recenctly, xscreensaver started binding to org.freedesktop.ScreenSaver on dbus. As a consequence, I cannot run them both anymore in parallel, cause the one I started after the other complains that a screensaver is already running. I read in the ArchWiki that there is some possibility to override services. But it is very vague and I'm not familiar with d-bus. Is there a way to have the two side-by-side without tampering with the source code of one of them? For the record: unsetting the DBUS_SESSION_BUS_ADDRESS environment variable before starting ether screensaver does not work. Edit: As far as I've seen in my research, it does not seem to be possible to prevent a program to listen to a d-bus service without causing trouble to this program. If someone can confirm me this, it would make a very good answer.

Some outputs are really great, IMHO. I have read all xscreensaver manual, but I cannot get it to work so I run a xscreensaver animation and then get a PNG (or TIF, or whatever). How can I make a virtual display so it can be screenshot? Or maybe can I somehow pipe out the output to a PNG/TIF file? Or is it possible to run each animation as standalone command?

The goal is to mute sound whenever screen lock happens. Ideally restore sound after unlocking as well. Sound system is Pulseaudio.

Hi I am running Debian 11 Bullseye, LXQt version, and I'm having trouble with the screensaver called XScreensaver version 5.45. * Basically what I would like to do is for the screen to completely shut off when I'm not using the computer for 10 minutes and for there to be a screen lock so when I or anyone else tries to go into the computer they need to type in my computer password. * However currently when I'm using this screensaver it's going to a blank screen which is a black screen but it is still giving some brightness so if I'm sleeping I will see this brightness. I want my screen to completely turned off, but to have the computer and some apps like FTP program gftp, transmission QT BitTorrent, or Firefox browser and of course the internet to be running. * Also, when I'm watching a movie/video or playing music, the xscreensaver activates and I have to put in my password every 10 minutes or so. Even if I change the settings temporarily and I put 720 minutes or something or even completely disable the screensaver, it still activates and I have to put in my password. I don't want the xscreensaver to activate at all when any audio or video application window is maximized. Only when the windows are minimized. I use VLC media player, Audacious, DeadBeef, and other audio and video players as well. I'm a newbie at this operating system, so how would I do this? Thank you so much

I'll start by stating, I'm pretty sure this is a unique mess of my own design, but I hope someone encountered this and might be able to help. ### The Setup My laptop runs Pop!_OS 22.04 (Based on Ubuntu Jammy). I really like the **xscreensaver** packages, but the Debian/Ubuntu/Pop!_OS release repos contain an outdated version, and only sid (aka Unstable) contains the updated package[*](https://www.jwz.org/xscreensaver/faq.html#upgrade "I was mistaken, and was working upon old habits"). No fret, that's why pinning exists, and so this is how I have it setup: > /etc/apt/preferences.d/unstable-200 file: >

> Package: *
> Pin: release a=unstable
> Pin-Priority: 200
>

> /etc/apt/preferences.d/xscreensaver-2000 file: >

> Package: xscreensaver*
> Pin: release a=unstable
> Pin-Priority: 2000
>

> /etc/apt/sources.list.d/debian.sid.list file: >

> deb [arch=amd64] http://http.us.debian.org/debian  sid main contrib non-free
>

This actually works, at this point running sudo apt install xscreensaver installs the updated versions. However, there is a strange side-effect. ### The problem When I run sudo apt update followed by sudo apt upgrade, I get the following output:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be DOWNGRADED:
  alsa-topology-conf appmenu-gtk-module-common aspell-en ca-certificates
  chrome-gnome-shell dictionaries-common dns-root-data emacsen-common folks-common
  fonts-arphic-ukai fonts-noto-cjk fonts-noto-cjk-extra fonts-noto-color-emoji
  fonts-urw-base35 friendly-recovery gir1.2-flatpak-1.0 gir1.2-gdkpixbuf-2.0
  gir1.2-graphene-1.0 gir1.2-gtksource-4 gir1.2-polkit-1.0 gir1.2-secret-1
  gir1.2-soup-2.4 gsfonts gsfonts-x11 hunspell-ar hunspell-de-at-frami
  hunspell-de-ch-frami hunspell-de-de-frami hunspell-en-au hunspell-en-ca hunspell-en-gb
  hunspell-en-us hunspell-en-za hunspell-es hunspell-fr hunspell-fr-classical hunspell-it
  hunspell-pt-br hunspell-pt-pt hunspell-ru hyphen-de hyphen-en-gb hyphen-es hyphen-fr
  hyphen-it hyphen-pt-br hyphen-pt-pt ieee-data javascript-common klibc-utils
  laptop-detect liba52-0.7.4 libappmenu-gtk2-parser0 libbytesize-common libffi8
  libflatpak-dev libgl1 libgles2 libgutenprint-common libgweather-4-0 libio-stringy-perl
  libjs-jquery libldacbt-abr2 libmpcdec6 libmysofa1 libopengl0 libpolkit-gobject-1-0
  libsndio7.0 libsoup-gnome2.4-1 libtermkey1 libvterm0 libwacom-common libxkbcommon0
  mythes-ar mythes-de mythes-de-ch mythes-en-au mythes-en-us mythes-es mythes-fr
  mythes-it mythes-pt-pt mythes-ru neovim-runtime netbase pass policykit-1 poppler-data
  powermgmt-base printer-driver-all python3-certifi python3-fido2 python3-jinja2
  python3-launchpadlib python3-lazr.uri python3-macaroonbakery python3-more-itertools
  python3-pkg-resources python3-pyatspi python3-rfc3339 python3-setuptools python3-tz
  python3-wheel python3-ykman sensible-utils sgml-base sgml-data sound-icons ssl-cert
  tpm-udev ucf update-inetd va-driver-all wamerican wbrazilian wbritish wfrench witalian
  wngerman wogerman wspanish wswiss xfonts-base xml-core yubikey-manager
0 upgraded, 0 newly installed, 125 downgraded, 0 to remove and 0 not upgraded.
Need to get 257 MB/283 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]

This also throws off Pop!_OS Shop's update count, with these packages showing as pending Operating System Updates. ## Troubleshooting Some data I collected while attempting to troubleshoot this. Removing /etc/apt/sources.list.d/debian.sid.list and running sudo apt update resolves the issue, so I know it's just a miscalculation/flawed logic somewhere. #### Focusing on the the first package in the list alsa-topology-conf: Although I know the error is completely superficial, at first I thought apt somehow tracks where (which repo) the package came from, so I removed, cleaned-up, then reinstalled the package. Didn't make a difference.

sudo apt remove alsa-topology-conf
sudo apt clean
sudo apt update
sudo apt install alsa-topology-conf

Running apt policy alsa-topology-conf, the results are: >

> alsa-topology-conf:
>   Installed: 1.2.5.1-2
>   Candidate: 1.2.5.1-2
>   Version table:
>  *** 1.2.5.1-2 200
>         200 http://http.us.debian.org/debian  sid/main amd64 Packages
>         100 /var/lib/dpkg/status
>      1.2.5.1-2 501
>         501 http://us.archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
>         501 http://us.archive.ubuntu.com/ubuntu  jammy/main i386 Packages
>

It seems that both sid and jammy have the exact same version, and for some reason, apt matches the package to the 200 priority, instead of the 501 priority entry. With /etc/apt/sources.list.d/debian.sid.list removed, the output looks like this: >

> alsa-topology-conf:
>   Installed: 1.2.5.1-2
>   Candidate: 1.2.5.1-2
>   Version table:
>  *** 1.2.5.1-2 501
>         501 http://us.archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
>         501 http://us.archive.ubuntu.com/ubuntu  jammy/main i386 Packages
>         100 /var/lib/dpkg/status
>

### Related questions The following are related questions with similar situations but none of the answers there helped me understand or resolve this. * https://unix.stackexchange.com/questions/270755/apt-pinning-priority-restricted * https://unix.stackexchange.com/questions/639180/debian-10-why-some-ssl-packages-will-be-downgraded * https://unix.stackexchange.com/questions/642951/how-to-get-rid-of-packages-were-downgraded-and-y-was-used-without-allow-down I've tried all of the answers in the above questions, but none seems to either be relevant or work out. # My question Does anyone have any suggestion on how to reconcile this so that the system will not constantly think that these packages need to be DOWNGRADED ?

I have a laptop where I tried xscreensaver auto blanking screen after 1 minute of idle time and even though everything seems idle it doesn't blank the screen. So then I ran this command to blank the screen manually: xset dpms force off This works but after a minute or two the laptop wakes up and the screen lights up again. How do I debug this? I want to know what process or event is happening that is making the screen turn on again after I manually turn off the monitors. Perhaps it's the same thing that is preventing xscreensaver from blanking the screen also?

A few days before, I wanted to try out xscreensaver as it is knows for its cool screensavers. So I installed that by: sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra But after trying it out, I found that this lock screen is not what I expected as it ask for login creds in xscreensaver that looks like this: This looked pretty ugly to me as my default screenlock was better. So I decided to remove xscreensaver from the system. So I ran sudo apt remove xscreensaver xscreensaver-gl-extra xscreensaver-gl But now, when I lock the system using the lock button found on the top right of my desktop, it doesn't lock itself. Thats when I realized I broke something. The lock button works fine if I am logged in as a root user. But doesn't work when I am the user that I always use. Here's my System Info:

$ uname -a
Linux  5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-1kali1 (2021-06-25) x86_64 GNU/Linux
$ neofetch

DE: Xfce 4.16

XScreenSaver uses DPMS to turn my laptop screen off. I'd like to find out why it's waking up to the prompt again. I enabled logging with log, but it shows nothing useful, > xscreensaver: 22:04:21: logging to "/tmp/f" at Thu Apr 26 22:04:21 2018 That's all that's in the log. Checking /var/log/kern.log, I see > xscreensaver: pam_ecryptfs: seteuid error How can I debug this issue, what are the likely causes of XScreenSaver waking my display up. I'm using xscreensaver 5.36.

xscreensaver doesn't show which is the current keyboard layout, so sometimes I can't enter my password, because I've switched to Cyrillic without knowing it. I found a discussion about the same problem at http://forum.xfce.org/viewtopic.php?id=6877 , for example. Is there a way to make it show the current keyboard layout, or always switch to English? My system is Debian Wheezy.

I am using Lubuntu, my desktop environment is lxQt and screensaver is xScreensaver. I'm trying to figure out a way to switch between users, (e.g. when pressing meta + L). Even though, it is possible to lock the screen with xscreensaver, I'm unable to use "new login" button and it shows this message: > could not excute "gdmflexiserver": No such file or directory **Update 1** I have come up with something I judge to be a hacky solution: creating a keyboard shortcut that triggers dm-tool switch-to-greeter. Although, as I said: it's more like a hack than a solution. It also makes me authenticate twice: once for LightDM and another for XScreenSaver, which is not very convenient.

How do I set up xscreensaver to run in the background on login? Will a simple xscreensaver & do the trick?

I have xscreensaver running as a user service and see that often it fails to start. The status shows DISPLAY not set. I've changed the service definition to now retry and that seems to be working [Unit] Description=XScreenSaver StartLimitInterval=200 StartLimitBurst=5 [Service] ExecStart=/usr/local/bin/xscreensaver -nosplash Restart=always RestartSec=30 [Install] WantedBy=default.target Is there a better way to do this? My guess is that because this is a user service it is starting sometimes before the user environment is fully set. Ideally the start would wait for DISPLAY to be set. The restart strategy seems crude but perhaps that's the best I can do.