usasite.blogg.se

1. ARCH XSCREENSAVER UNABLE TO FIND ANY ALTERNATIVE INSTALL
2. ARCH XSCREENSAVER UNABLE TO FIND ANY ALTERNATIVE MANUAL

If it is still suspending, have you rebooted or restarted logind after making those changes to nf? You can't just edit the file and have the changes implemented right away, as the configuration is parsed and the settign implemented on the service start. Anyway to make this work I want my screen to be locked when I hibernate.

However when I resume from hibernate it goes straight back to my desktop, no locked screen. xscreensaver & xscreensaver-settings HOW IT WORKS When it is time to activate the screensaver, a full-screen black window is created that covers each monitor. My screen locks like it is supposed to when suspend, so I need to enter my password on resume. You configure it with the xscreensaver-settings (1) program. alternative to Windows, no question there, but I cant see them becoming.

ARCH XSCREENSAVER UNABLE TO FIND ANY ALTERNATIVE INSTALL

To see what kinds of things trigger a udev event, you can use udevadm monitor or if you install acpid, there is the acpi_listen option.Įdit2: BTW, what is it you mean by not working? Does it still suspend on lid close, or is your xscreensaver not started? You need to be more explicit there. GETTING STARTED XScreenSaver is a daemon that runs in the background. sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra. Hi Angela, Try cleaning the repo cache at your local host: apt-get clean apt-get update. It can allow for one central script (or collection of scripts) to handle all the different events that udev sends.

ARCH XSCREENSAVER UNABLE TO FIND ANY ALTERNATIVE MANUAL

But it is a much easier method of setup since it simply relies of basic scripting in order to make it work. General Commands Manual XScreenSaver (1) NAME xscreensaver - extensible screen saver and screen locking framework SYNOPSIS xscreensaver -display host:display.screen -verbose -version -no-splash -log filename DESCRIPTION XScreenSaver waits until the user is idle, and then runs graphics demos chosen at random. I would recommend using acpid, as it is much more flexible in what it can allow you to do.Įdit: acpid is not necessarily more flexible than a udev rule, as it relies on the udev events. The lid switch sends an event to udev, so you have the option of having a udev rule that responds to this, or using acpid to start this for you. Therefore, you are going to have to have some other way of triggering actions in response to these events. So if it is set to ignore the lid switch, then it obviously isn't going to be entering the suspend.target (or is it the sleep.target, I can't remember). But I checked them again and they all look correct.

I haven't made changes to the xscreensaver settings in a long time. I would say that you should just have logind ignore the LidSwitch altogether. I don't know quite what has triggered this - or even if this bug is necessarily in the xscreensaver code - but my screen saver has stopped engaging as of about a week ago.