What's the better cross-DE way to disable the screensaver in Linux? I found something here but it's only for gnome-screensaver. I'm wondering if there's any way to simulate a keystroke or some X.Org API to disable screensaver activation.
I don't really like the call to xwininfo and wish there was a cleaner way but so far could not find anything better. Another issue with the xwininfo approach is that it uses the id of the root window instead of the app window. Using the app window id instead of the root window would remove the need for the resume_screensaver method since it would then resume as soon as the window is destroyed.
Rhel 7 Screensaver Download
Download Zip 🔥 https://blltly.com/2yGAvd 🔥
After having used the python solution above for over a year, it was found to occasionally create zombie processes and/or too many instances of xdg-screensaver, so after digging around, I found a simpler alternative which is Gnome-specific, but works for me even in a non-Gnome DE (XFCE) since the core Gnome libraries are required by many GTK-based apps even if you don't have a Gnome desktop.
TLDR; there aren't any cross-DE ways to inhibit the screensaver with pure Python. However the question also asked about doing so with Linux (presumably from the shell). To be clear, there aren't any particularly good cross-DE ways to do so in Linux, but at least there is potential. You probably want to use the hackish xdg-screensaver shell script.
This is a topic I've spent some time on. I wasn't happy with any of the solutions out there, so after playing around with some homebrew tools, I ended up modifying the caffeine project to suit my needs and have been using it happily ever since. I'll summarize some of what I've learned in the process.
The first half of ccpizza's answer is great as it is cross-DE and very similar to caffeine's implementation. I haven't had any issues with xdg-screensaver zombie processes but I'm sure it could be remedied if I better knew the use-case or the conditions under which it was occurring. Just a FYI that running xdg-screensaver suspend ROOT_WINDOW_ID will background a tracking process and leave it running indefinitely (until it is resumed).
If you're interested in implementing a truly cross-DE solution then I would strongly recommend examining the aforementioned xdg-screensaver/caffeine-screensaver. The many forks of lightsOn are ripe as well.
xdg-screensaver detects the desktop environment (KDE, Gnome, XFCE, LXDE, xscreensaver, or gnome-screensaver) and acts accordingly. For the xdg-screensaver suspend command, it runs xset -dpms to disable DPMS, DE-specific commands, then watches the supplied window ID for it's duration. If the window disappears, the resume command is run and xdg-screensaver exits. The xdg-screensaver resume command consists of xset +dpms (only if DPMS was originally enabled) then the DE-specific commands.
Note that xdg-screensaver will only track the supplied window ID if xprop is available (it's part of x11-utils, so it should be). To track the window, it backgrounds xprop -id WINDOW_ID -spy to monitor the window for changes. It stores the PID of the aforemention process along with window ID in a lockfile to reference upon suspend and resume. The original state of DPMS is referenced in a separate lockfile. The lockfiles should ensure there are no duplicate processes.
The script is a complete mess, so I empathize with anyone unfortunate enough to use it, but I haven't encountered any issues. You probably don't want to reinvent the wheel so if you are creating something for public consumption then I'd recommend you just co-opt it. If you're creating something for personal use, then just dig through it and use the commands specific to your DE.
ccpizza suggesting using subprocess.Popen('xwininfo -root | grep xwininfo | cut -d" " -f4', stdout=subprocess.PIPE, shell=True).stdout.read().strip() to get the desktop's root window ID. Using the desktop's root window ID with xdg-screensaver suspend will disable the desktop's screensaver indefinitely. Using a specific window's ID will disable the desktop's screensaver for the duration of the window.
I am not sure what am I doing wrong. I am suspecting that this will not work with cinnamon-screensaver-command because all examples I have seen uses something like slimlock or xlock, but I would really like to understand what is going on.
The issue is resolved on its own though. I think maybe a restart was needed, which is probably weird?
For my knowledge the changes in systemd should be active once I enable them with --now option.
Hey! I installed the gnome-screensaver. The journalctl now reads:
Couldn't lock screen: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
ran dconf and went to org.gnome.desktop.lockdown and set the key disable-lock-screen to [false] I don't know why it was set to true
Problem solved I can now press Super + L and the screen lock right away.
After Linux 5.10 is finally recommended as a kernel, I decided to take it another shot.
It seems like I still have this lockscreen issue which prevented me from upgrading to the new kernel version earlier.
Thus I ask for support on this issue.
I get the feeling that I installed light-locker for a reason, like xfce4-screensaver was unable to go completely black or something, or maybe I had the same issues with it as I have with light-locker right now.
In a last ditch effort to get this sorted, I removed the xscreensaver package. Alas, this did not solve the issue. The screen still blanks after a length of time. I have however managed to disable the 'screenblanking' with the xset utility. However cannot get it to persist after reboot.
Add your xset commands to a startup script - a script can be scheduled to run during startup from Session_and_Startup-->Application_Autostart. But beyond that, check and disable the monitor settings in the preferences for xfce4-power-manager too.
I have created an Autostart script with xset commands for disabling screen blanking and gone into the Settings-->Session_Startup-->Application_Autostart menu and added an option to execute my Autostart script. On exiting and restarting Xfce4 and running xset -q I see the Screen Saver prefer blanking is back at 'yes'. If I go into the terminal emulator and type in 'xset s noblank' (or execute my Autostart script) and check the settings with xset -q again the prefer blanking is 'no'. So my commands are correct, but either my Autostart script is not being executed, or the order of scripts is such that there is some other script overriding my Autostart.
In Settings-->Session-->Startup--Application_Autostart create a new application (click on the + and the system generates a new line). Fill in the fields, but the important bit is in the 'Command' field, enter
Make sure you include the zsh (or sh depending on which version of Linux you are using). The other critical bit is to go to the Power Manager and enable it (not disable). Set the option for Timeout and Screen blank to 'never'. And that should do it.
I was led down the wrong path in my journey to finding the solution by reports on the internet that there was some sort of bug in Debian, Raspbian. In fact the actual problem is the apparent dearth of documentation that makes it clear just how Debain (Bananian) and Xfce work together. I hope this is of some use to others that have the same problem.
Option "BlankTime" "time"sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xorg server's `-s' flag, and the value can be changed at run-time with xset(1x) . Default: 10 minutes.
Option "StandbyTime" "time"sets the inactivity timeout for the "standby" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x) . Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below).
Option "SuspendTime" "time"sets the inactivity timeout for the "suspend" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x) . Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below).
Option "OffTime" "time"sets the inactivity timeout for the "off" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1x) . Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below).
This all worked extremely well, until we recently switched from our in-house web server to a hosting service targeted at libraries. They offered integration of other services we wanted to start using, making it easy to have these services available to our patrons with just a few mouse clicks instead of having to spend tons of time and a steep learning curve on the part of our part-time, in-house web developer.
The problem is that the new host appears to include the code to disable screensavers somewhere in the main templates of every webpage, preventing my script to reset Firefox after a time with no keyboard or mouse activity from working reliably.
You might be able to block the file/URL the same way you are blocking access to other sites. You may need to visit the page in Chrome or Firefox and view the source or dev tools looking for as a tag, or some video format.
As a fellow library IT pro, I would be happy to send you a .PDF copy of my directions for setting up a catalog kiosk using the exceptionally inexpensive Raspberry Pi 400. PM me with your email address if you are interested. 152ee80cbc
download make it rain by fat joe
dream catcher trance mp3 download