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. It can allow for one central script (or collection of scripts) to handle all the different events that udev sends. But it is a much easier method of setup since it simply relies of basic scripting in order to make it work. I installed xorg, i3-gaps, and changed my /.xinitrc file to read: xrandr -setprovideroutputsource modesetting NVIDIA-0 I installed Arch on my laptop yesterday and since then I have been unable to open i3. 1 15:55:23 Der Chefkoch Member Registered: Posts: 99 I am running Budgie Desktop and while I am very happy with it, the Screensaver is giving me quite some issues (as Budgie is presently only providing a temporary fork of gnome-screensaver etc. xinitrc and can confirm that my screen does not blank. xset s noblank don't blank the video device exec /etc/alternatives/x-session-manager start lxde This file runs once every time X starts and should solve the problem. 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. xset s off don't activate screensaver xset -dpms disable DPMS (Energy Star) features. niowluka Re: Xscreensaver error 'Can't open display: :0.0' by niowluka Tue 12:25 pm Does it work without sudo I can't really think of a reason why you would want to invoke it like that. 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. To install you need sudo apt-get install xscreensaver. Using this option also implies verbose output. Only way Ive been able to fix this issue is install xscreensaver. To save the log to a file, you can set the path using the -log option. You can also add verbose: True to the /.xscreensaver file to make it persistent. 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). To log verbose debugging information, start xscreensaver with the -verbose command line option. I would say that you should just have logind ignore the LidSwitch altogether.
0 kommentar(er)
