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/) .

Web search found https://superuser.com/questions/363347/transparent-screensaver-for-linux , which dated 2011, recommends xlock -mode blank -geometry 1x1, I'm on Linux Mint based system and seems official repos do not have xlock, so I figure maybe it's outdated for modern Linux. What can I use now in place of the above? Or maybe a program for xscreesaverthat just does see-through of the screen. TIA

I want my screen to stay EXACTLY the same after it's finished booting, forever, which means I NEVER want it to go black, and I NEVER want to see that clock overlay appearing over the top of my username selection login dialog (it's a VM - has no real monitor, so all this blanking and screen saving garbage makes no sense). Basically - when something goes wrong, like a kernel problem, I can't see on the console what that was, since it's gone black and only shows up if a key is pressed, which (in the case of kernel issues) doesn't always still work. I've already included this on my boot line:

=0

I've tried this:-

set org.gnome.desktop.session idle-delay 0

I've even tried this:-

-rf  /usr/bin/xdg-screensaver /usr/lib/python3.6/site-packages/orca/scripts/apps/gnome-screensaver-dialog /usr/lib64/libxcb-screensaver* /usr/lib64/pkgconfig/xcb-screensaver* /usr/lib64/totem/plugins/screensaver /usr/libexec/gsd-screensaver-proxy

I'm in runlevel 5 - I'd prefer not to go back to 3 ( which consoleblank=0 works for ). Anyone got any clues? Basically - I never want to see this timewasting dumb idea again (or it's evil cousin - the near-totally black version [go mousey, you at least escaped the blackout!!]):-

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 am using Ubuntu-based KDE Neon and recently added a new user to my machine. Ever since I added the new user, whenever the machine goes to sleep - usually due to inactivity - the screen stays black, no matter what I do. The only thing that is visible is the cursor and it disappears when I press escape key and appears when I press anything else. This laptop has an AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx. I do not dual boot and kernel is Linux 6.8.0-52-generic x86_64, the operating system is KDE Neon 6.2 with release 22.04 (jammy), and the laptop is an Asus VivoBook X512DA.

After my most recent pamac update my system now has a screen timeout/lock enabled which I didn't have set up before. This seems to stem from light-locker having a _lock after screensaver 5_ setting showing via light-locker --debug, but I don't know what settings the update actually modified since the power manager still claims the screen should never sleep. So how can I figure out what has been modified without my consent and fix this again?

Currently I have my machine configured with xss-lock like so: exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock -i /home/wayne/bluetuith/me.png --nofork I needed this to enable udev to lock my screen when I pull my Yubikey out with this udev rule: ACTION=="remove", SUBSYSTEM=="usb", ENV{PRODUCT}=="1050/402/543", RUN+="/usr/bin/loginctl lock-sessions" However... it *also* locks my screen when the monitor blanks. Which I don't actually want. I tried with xset 0 0 (relevant output of xset q) Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 0 (To be precise, I only tried with xset 0 before writing this so it's possible that 0 0 does it but I'm pretty sure not, since xset dpms force standby still locks the screen which I don't *think* that I want) How do I make it so that my screen locks *only* when: 1. I remove my Yubikey 2. I close my lid And not just when the screen goes dark/blank from DPMS? --- **Edit**: xss-lock --ignore-sleep *kindof* helps -- closing the window lid won't actually make it lock, but pulling the Yubikey out and: bindsym Control+$mod+l exec i3lock -i ~/bluetuith/me.png allows me to quickly lock it but... I haven't figured it how to lock it on lid close.

OS: MX Linux 23.4 Just noticed after the last 2 system update that my screen after going to dormant/suspend can't wake up. I've setup my F7 to turn off the screen, it seems this is not the cause, because if I move my mouse few minutes after turning off the screen by activating F7 key, it works, but if the time is longer (probably between 10-15min, not sure, hasn't timed it), moving the mouse won't turn on the screen (it seems the OS stopped sending signal to monitor, I haven't noticed this behavior before the last 2 updates). The command I'm using for F7 key is xset dpms force off. What am I missing? Is there another way to "wake up" Linux? Currently the only way I found is "hard shut down" (press ON button for few seconds, then the pc shuts down), which I'm pretty sure is not recommended. ps: I've posted this question on MX forum, still waiting for reply.

I want to turn off the screen after 10 minutes of inactivity, and 1 minute later, **IF** the monitor is still off, then lock the screen. I know how to turn the screen off with dbus, how to lock screen, and how to get the screensaver state (i.e., if the screen is locked). But I do not know how to get the current monitor state ON/OFF. So I want for KDE to trigger this script after 10 minutes of inactivity: #!/bin/bash sleep 1 dbus-send --session --print-reply --dest=org.kde.kglobalaccel /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut string:'Turn Off Screen' sleep 60 [[ ]] && dbus-send --session --print-reply --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock So how to query for monitor state (preferably with dbus), namely, the `` condition in the above script? I used to do xset -q | grep -i 'monitor is off', but now I get an error: Server does not have the DPMS Extension.

I want to do a bunch of tasks before and after the screensaver is activated in KDE (*still* using X11, since Wayland has too many flaws even after 10 years). So I made a custom script that is triggered after 5 minutes of inactivity (KDE settings > Power Management > Other Settings). The problem: when I come back and press a key, KDE takes around 8 seconds to show the desktop, and when it does, it is not quite ready, turns the screen off/on, moves things around, blinks, etc, during around 6 to 8 seconds more until it is finally back from the Dead. Probably that consumes more energy than keeping the screen on! This is my script: #!/bin/bash sleep 2 xset dpms force off If instead of the xset line I put the next line the problem persists: dbus-send --session --print-reply --dest=org.kde.kglobalaccel \ /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut \ string:'Turn Off Screen' So: why is KDE making such a mess, and how can I prevent it? Or maybe there is a better way to do this? I would love to know your own way.

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.

Bonjour, Is it possible to run a terminal at full screen running a script instead of the screen saver ? That means that after 10 minutes of inactivity the screen should go black and show the STDOUT of a script (ex cmatrix or fortune), and then go away when clicking with the mouse / with a keystroke. I'm running Antergos (ArchLinux) with the last version of Gnome. If you have any ideas on how I could do this, I would really appreciate.

After KDE plasma 6 update, my CPU usage increased significantly while on lockscreen. This caused the processor to reach high temperatures and lose electricity unnecessarily. Main processes that caused this were:

Xorg --nolisten tcp [...]    # ~ 60% CPU usage
kwin_x11 --replace           # ~ 40% CPU usage
kwin_x11 --replace           # ~ 20% CPU usage

I suspect it has something to do with the multi monitor setup. **Solution:** To fix this you need to: 1. go to system settings > Display and Monitor > Compositor 2. Uncheck Enable on startup 3. Confirm 4. Reboot After that CPU usage on lockscreen goes back to normal.

I have re-installed Debian 7 (Wheezy) after a while. For the first time, I am using the open-free Nvidia drivers (not nouveau) and vesafb for virtual consoles. I cannot, for the life of me, stop the screen from blanking. There is no screensaver, nothing, it just goes blank, just after a couple of minutes of inactivity. This is not just during VLC (which has had such an issue in the past) but during anything. To make it worse, it seems to happen at random.  Sometimes the screen will not go blank for hours, and sometimes it will. Steps I have taken so far: 1. Added a few lines in /etc/X11/xorg.conf to stop dpms: Section "ServerLayout" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" ... Section "Monitor" ... Option "DPMS" "false" 2. Added in my .xinitrc file: xset s off # don't activate screensaver xset -dpms # disable DPMS (Energy Star) features. xset s noblank # don't blank the video device 3. Disabled ALL screensavers and power saving modes under KDE settings. 4. Added the following loop in my /etc/init.d/rc.local: for index in $(seq 1 6) do setterm -blank 0 -powerdown 0 -powersave off > /dev/tty${index} done 5. Patched my xdg-screensaver with a patch I found that was forcing VLC to spawn a screensaver.  (I have since stopped using VLC and reverted to Dragon player.) This is turning into a nightmare, and is truly very annoying. Before I nuke vesafb and setterm (which I have the feeling are somehow responsible for this) I would like to know if anyone has ever run into this problem, and how they managed to solve it.

In my .sway/config, I have exec swayidle -w \ timeout 30 'swaylock -f -c 000000' \ timeout 30 'swaymsg "output * dpms off"' \ resume 'swaymsg "output * dpms on"' \ before-sleep 'swaylock -f -c 000000' Let's say I decide that I want to increase that timeout, so I make it, exec swayidle -w \ timeout 180 'swaylock -f -c 000000' \ timeout 180 'swaymsg "output * dpms off"' \ resume 'swaymsg "output * dpms on"' \ before-sleep 'swaylock -f -c 000000' How can I reload these settings? Moreover, when I try to killall swayidle and run this command manually, I get Failed to find session name: PID 8472 does not belong to any known session No command specified! Nothing to do, will exit How can I get swayidle running with updated timeouts?

In Ubuntu 22.04 with Gnome, how can I 'wake up' the screen programmatically once it is has blanked due to user inactivity? I tried the following:

gdbus call --session --dest org.gnome.ScreenSaver --object-path /org/gnome/ScreenSaver --method org.gnome.ScreenSaver.SimulateUserActivity

But received an error indicating that SimulateUserActivity is an unknown method (verified using '***gdbus introspect***') I then tried:

dbus-send --system --type=signal /org/gnome/ScreenSaver org.gnome.ScreenSaver.WakeUpScreen

Unsurprisingly, that also did not work (no error, but screen stayed blank) Finally, I tried using ***xdotool*** to simulate keypresses and mouse moves. Screen still stayed blank.

I regularly observe this behaviour on one particular system: * I lock the screen either manually or by idling for the configured time * screen turns black and shortly after the screen enters power-save * I try to unlock it by pressing a key or moving the mouse * **screen turns on, but *without* the screen lock, showing the regular desktop** * I can move the mouse and see the cursor move * windows display a fresh image (not the one when the screen should have locked) * after **a few seconds** something remembers that the screen was to be locked and **then** hides the regular desktop and shows the password prompt * entering the correct password then correctly unlocks the screen I have never seen this before and I run basically the same setup on most of my systems, past and present. And I have not seen this happen with the same system on a different physical screen. This is currently more of a nuisance but I worry about it also being a security problem. Potentially this might allow people without the correct credentials to unlock the system permanently. The system is set up as this: * Linux kernel 6.7.12 * debian trixie/sid * lightdm * mate as session manager * **mate-screensaver** (default) * xmonad as window manager (replacing marco in mate) * LG screen and a (somewhat older) AMD/ATI Radeon card I suspect lightdm mate-screensaver to be the culprit but **I don't know how to troubleshoot this**. I also have only observed this with the specific LG screen, but what the system decides to display in this context should theoretically not depend on what screen is plugged in.

I was on Jessie, did an upgrade to Stretch and then immediately to Buster. I believe I have the default gnome 3 desktop manager. If I lock the screen with super-l then I cannot wake the screen up again with the mouse or keyboard (but scroll lock/num lock do toggle the keyboard LEDs). This also happens if I do not log in after boot, the login screen auto locks after 5 minutes. I think the 5 minutes is coming from org.gnome.desktop.session idle-delay uint32 300, so setting that to 0 might stop it from auto locking, but that does not explain why it does not turn back on. Note that the machine does not suspend, just turns off the monitor. I believe I disabled suspend with org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'. This is a desktop, always on AC, never battery. I can bring the screen back over ssh with:

sudo systemctl restart gdm.service

Some gsettings that might indicate something:

$ gsettings list-recursively org.gnome.desktop.screensaver
org.gnome.desktop.screensaver picture-opacity 100
org.gnome.desktop.screensaver logout-enabled false
org.gnome.desktop.screensaver lock-enabled false
org.gnome.desktop.screensaver logout-delay uint32 7200
org.gnome.desktop.screensaver embedded-keyboard-enabled false
org.gnome.desktop.screensaver primary-color '#023c88'
org.gnome.desktop.screensaver idle-activation-enabled true
org.gnome.desktop.screensaver secondary-color '#5789ca'
org.gnome.desktop.screensaver logout-command ''
org.gnome.desktop.screensaver color-shading-type 'solid'
org.gnome.desktop.screensaver embedded-keyboard-command ''
org.gnome.desktop.screensaver picture-options 'zoom'
org.gnome.desktop.screensaver lock-delay uint32 0
org.gnome.desktop.screensaver show-full-name-in-top-bar true
org.gnome.desktop.screensaver picture-uri 'file:///usr/share/images/desktop-base/desktop-lockscreen.xml'
org.gnome.desktop.screensaver status-message-enabled true
org.gnome.desktop.screensaver user-switch-enabled true
$ gsettings list-recursively org.gnome.desktop.session
org.gnome.desktop.session session-name 'gnome'
org.gnome.desktop.session idle-delay uint32 0
$ gsettings list-recursively org.gnome.desktop.lockdown
org.gnome.desktop.lockdown disable-command-line false
org.gnome.desktop.lockdown disable-application-handlers false
org.gnome.desktop.lockdown disable-user-switching false
org.gnome.desktop.lockdown user-administration-disabled false
org.gnome.desktop.lockdown disable-printing false
org.gnome.desktop.lockdown disable-log-out false
org.gnome.desktop.lockdown disable-lock-screen false
org.gnome.desktop.lockdown disable-print-setup false
org.gnome.desktop.lockdown disable-save-to-disk false
org.gnome.settings-daemon.plugins.power power-button-action 'interactive'
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1800
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600
org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30


$ sudo -u Debian-gdm gsettings list-recursively org.gnome.desktop.screensaver
org.gnome.desktop.screensaver picture-opacity 100
org.gnome.desktop.screensaver logout-enabled false
org.gnome.desktop.screensaver lock-enabled true
org.gnome.desktop.screensaver logout-delay uint32 7200
org.gnome.desktop.screensaver embedded-keyboard-enabled false
org.gnome.desktop.screensaver primary-color '#023c88'
org.gnome.desktop.screensaver idle-activation-enabled true
org.gnome.desktop.screensaver secondary-color '#5789ca'
org.gnome.desktop.screensaver logout-command ''
org.gnome.desktop.screensaver color-shading-type 'solid'
org.gnome.desktop.screensaver embedded-keyboard-command ''
org.gnome.desktop.screensaver picture-options 'zoom'
org.gnome.desktop.screensaver lock-delay uint32 0
org.gnome.desktop.screensaver show-full-name-in-top-bar true
org.gnome.desktop.screensaver picture-uri 'file:///usr/share/images/desktop-base/desktop-lockscreen.xml'
org.gnome.desktop.screensaver status-message-enabled true
org.gnome.desktop.screensaver user-switch-enabled true
$ sudo -u Debian-gdm gsettings list-recursively org.gnome.desktop.session
org.gnome.desktop.session session-name 'gnome'
org.gnome.desktop.session idle-delay uint32 300
$ sudo -u Debian-gdm gsettings list-recursively org.gnome.desktop.lockdown
org.gnome.desktop.lockdown disable-command-line false
org.gnome.desktop.lockdown disable-application-handlers false
org.gnome.desktop.lockdown disable-user-switching false
org.gnome.desktop.lockdown user-administration-disabled false
org.gnome.desktop.lockdown disable-printing false
org.gnome.desktop.lockdown disable-log-out false
org.gnome.desktop.lockdown disable-lock-screen false
org.gnome.desktop.lockdown disable-print-setup false
org.gnome.desktop.lockdown disable-save-to-disk false
$ sudo -u Debian-gdm gsettings list-recursively org.gnome.settings-daemon.plugins.power
org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 1200
org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30

## Update ## I edited /etc/gdm3/daemon.conf and uncommented WaylandEnable=false:

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

Now the screen comes up properly when I press a key. So it would seem it is something Wayland related. I have no idea on how to debug it or how to enable more verbose logging to try to narrow down the issue. More info:

$ sudo lspci -nnk | egrep "VGA|3D|Display" -A2
0b:07.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02)
        Subsystem: Dell PowerEdge T300 Embedded ATI ES1000 [1028:0210]
        Kernel driver in use: radeon

When I'm using my laptop if I don't use it for a while, the laptop's screen goes off and the external monitor turns off by itself. I'm trying to prevent my second monitor from turning off, and I want it to remain a blank black screen for a given period of time when the system passes to an idle state. I'm connecting a second screen to my laptop by an HDMI cable to an LCD screen. I use Debian 12 (bookworm), and I use gnome-43.9 desktop environment. I also use the Wayland windowing system. I tried xset s off and it didn't effect anything. There was no error when executing this command. When I tried xset -dpms I got this error message: server does not have extension for -dpms option I looked up similar questions and other Stack Exchange forums, but I couldn't find a way to get around this problem.

In [awesome window manager](https://awesomewm.org/) , my screen brightness gets reset to 100% each time I'm away from my computer for a few minutes. **How can I get it to sustain the brightness I set prior to these screen-saver/power-management timeouts?** **Background:** Using [autokey](https://en.wikipedia.org/wiki/AutoKey) , I've created 3 scripts that enable me to adjust my screen's brightness with hotkeys. These scripts use the debian package brightnessctl to accomplish this:

sudo apt install brightnessctl

` For the sake of being helpful to others, I will include these scripts below. **Increase Brightness:**

import os
currentBrightness = system.exec_command("brightnessctl g")
brightnessLevel = str(int(currentBrightness) + 1)
if int(brightnessLevel) > 100:
    brightnessLevel = '100'
if brightnessLevel:
    cmd = "brightnessctl s " + brightnessLevel
    os.system(cmd)
    store.set_global_value("lastBrightness",brightnessLevel)

**Decrease Brightness:**

import os
currentBrightness = system.exec_command("brightnessctl g")
brightnessLevel = str(int(currentBrightness) - 1)
if int(brightnessLevel)  0:
    store.set_global_value("lastBrightness",brightnessLevel)
    cmd = "brightnessctl s " + brightnessLevel
    os.system(cmd)

While these scripts are working perfectly, I do have an issue: When I'm away from my computer for a few minutes, and then come back, my monitor will be in some type of power saving state, where the monitor has been either turned off or displays a black screen. When I wake up the monitor (by hitting a key or moving my mouse) the brightness that I previously set (using brightnessctl), has been changed back to 100% brightness. **How can I sustain my brightness settings thorough these screen-saver/power-saving timeouts?**