Hello,
I have a new install of Qubes 4.2.rc1 and can’t get xscreensaver working properly.
The screen blanks after the given time but won’t switch off.
The xscreensaver app from xfce seems not available anymore/does not start, so I don’t know how to get a working setup.
What else I have done up to now:
Tried xfce4-power-manager
Does not give expected result (same as Qubes 3.2 up to Qubes 4.1)
Edited the files manually:
/usr/share/X11/app-defaults/XScreensaver
Edited the files manually:
/etc/xscreensaver/XScreenSaver.ad.header
and run
/usr/sbin/update-xscreensaver-hacks accordingly
Inside XScreensaver I changed:
*dpmsEnabled True
*dpmsQuickoffEnabled True
*dpmsStandy 0:10:00
*dpmsSuspend 0:10:00
*dpmsOff: 0:10:00
So my question is why the screen does not switch off after 10 min.?
opened 09:07AM - 26 Apr 19 UTC
T: bug
C: desktop-linux
P: minor
hardware support
needs diagnosis
affects-4.1
**Qubes OS version**
R4.0, kernel-latest
**Affected component(s) or function… ality**
X11
**Brief summary**
Activate the lock screen. The backlight stays on.
**To Reproduce**
See summary.
**Expected behavior**
While the screen is locked the backlight should be turned off.
**Actual behavior**
It glows eerily in the dark.
**Additional context**
Backlight control on Lenovo P52 with nouveau started working with kernel 5.0.7 BUT currently requires a modified xen.cfg enty:
kernel=vmlinuz-5.0.9-1.pvops.qubes.x86_64 [...] acpi_backlight=vendor acpi_osi="Linux" thinkpad-acpi.brightness_enable=1 nouveau.modeset=1 [...]
It seems that the currently used lockscreen is not up to the task and also cannot be configured to use alternative ways of controlling screen brightness.
**Solutions you've tried**
Installing Arch Linux helps tremendously.
Please consider replacing the component.
opened 08:36PM - 14 Feb 18 UTC
T: bug
P: major
C: desktop-linux-xfce4
hardware support
affects-4.1
#### Qubes OS version:
<!-- (e.g., `R3.2`)
You can get it from the dom0 t… erminal with the command
`cat /etc/qubes-release`
Type below this line. -->
R4.0-rc4
---
### Steps to reproduce the behavior:
In `xfce4-power-manager-settings` adjust the display to suspend and/or power off after a set time, then wait.
### Expected behavior:
As with R3.2, monitor goes into standby/suspend/low power mode.
### Actual behavior:
Monitor display is blanked, but remains fully powered-on.
### General notes:
This may be related to the fact that I used KDE on R3.2, and now I use Xfce on R4.0.
---
#### Related issues:
Maybe issue #2212
@adw these issues look the same to me. One could probably be closed as a duplicate.
There is a workaround:
@trounces :
remains blank so in the dark you can continue to see the blank screen glowing light
I have the same issue sometimes under R4.0. What always fixes it for me:
open “Scrensaver”
File | Restart Daemon
Advanced | Display Power Management …
uncheck and re-check “Power Management Enabled”
uncheck and re-check “Quick Power-off in Blank Only Mode”
The last option is the one that needs to be checked for the effect you wish to see. However every now and then it seems to stop working an…
3 Likes
quantum
September 7, 2023, 1:34pm
3
This workaround does not function on R4.2.0-rc3.
xscreensaver, nor xscreensaver-settings may be started from the command line.
szz9pza
September 7, 2023, 2:00pm
4
opened 09:31PM - 14 Jun 23 UTC
T: bug
C: desktop-linux-xfce4
P: default
diagnosed
waiting for upstream
affects-4.2
[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/)
#… ## Qubes OS release
v4.2
### Brief summary
XScreenSaver & XScreenSaver Settings not opening window in Dom0.
### Steps to reproduce
Click XScreenSaver or XScreenSaver Settings from System Settings Menu
### Expected behavior
Opens Screensaver settings window as in v4.1.2.
### Actual behavior
If typing "xscreensaver" in the dom0 terminal it says the task is already running and the window is open. Nothing appears on the screen.
Version 6.06-3-fc37 of xscreensaver is available in fedora-update repository.
BUT qubes-dom0-update does not fetch it unless explicitly calling
sudo qubes-dom0-update xscreensaver-6.06-3.fc37.x86_6
then xscreensaver-setting works.
dom0
actual version (4.2.0-rc3) is 6.06-1.fc37
.
I didn’t try, you can report back if it works for you.
quantum
September 7, 2023, 5:20pm
5
4.2.0-rc3 uses 6.1.43-1 with fresh install.
Thought the later kernel would have the fix.
szz9pza
September 7, 2023, 6:00pm
6
We are not talking about kernel version.
We are talking about xscreensaver
version.
quantum
September 7, 2023, 7:31pm
7
Thanks.
Correct dom0 command is
sudo qubes-dom0-update xscreensaver-6.06-3.fc37
szz9pza
September 7, 2023, 8:15pm
8
Yes the command is:
sudo qubes-dom0-update xscreensaver-6.06-3.fc37
or (there is a missing letter in the github comment)
sudo qubes-dom0-update xscreensaver-6.06-3.fc37.x86_64
You could (and should) also disable weak dependencies installation:
sudo qubes-dom0-update --setopt=install_weak_deps=false xscreensaver-6.06-3.fc37
However.
If you install xscreensaver
from fedora repo, you will notice a downgrade:
Downgrading:
xscreensaver-base x86_64 1:6.06-3.fc37 qubes-dom0-cached 492 k
When your search for installed packages, you got this:
[user@dom0 ~]$ sudo dnf list --installed | grep -i screensaver
xscreensaver-base.x86_64 2:6.06-1.fc37 @qubes-dom0-cached
Notice the 2:
in the installed package and the 1:
in the downgrade.
It’s called an Epoch tag.
My guess:
Qubes OS did modify xscreensaver
to include some fix / improvement.
They probably installed it in dom0
with an Epoch Tag of 2 to avoid the package to be updated by the fedora repository.
I can not confirm, I don’t know. But I strongly think that is correct.
@rustybird ?? @unman ??
The Qubes OS logo replaces the default flames on Qubes OS, that might be the change.
Related to that change: Default Screensaver (can I change the image back to the old one)
szz9pza
September 7, 2023, 9:23pm
10
1 Like
steffen
September 20, 2023, 7:22pm
11
xscreensaver-settings still does not open a window as of today after updating everything.
However I found out a setting inside of Power Manager that switches off the display at least.
Note to “Blank after” and “Put to sleep” after are both set to “Never” and the switch off time can be choosen (here 10 minutes).
szz9pza
September 20, 2023, 7:50pm
12
the fix is currently in testing repository.
https://github.com/QubesOS/qubes-issues/issues/8266#event-10404152432
To get it, you need to enable testing repository:
Qubes Menu > Settings > Qubes Tools > Qubes Global Config > Updates: Dom0 Updates: Enable all testing updates
If your still in 4.2-rc1, to update to 4.2-rc3, you also need to enable this repository.
Once you enabled it, process a normal update of dom0
.
1 Like