Display turning off instead of blanking in X11 on Bookworm image
-
We are running the Bookworm image under X11 instead of Wayland due to the lack of on-screen keyboards available for Wayland that work on the Raspbian image. I'm fairly certain Wayland has the expected behavior, where the display gets blanked but remains on, so a tap on the touch screen wakes it, but under X11 the display turns off, which requires turning it back on and tapping repeatedly in a "safe" location until the Pi wakes up (safe in this instance means a location unlikely to cause undesired machine behavior). This is a change from the older Bullseye image, which worked as expected.
I'm assuming this is simply a configuration issue. A setting which was set for X11 on the older image is not set for Bullseye since the assumption is you will be running under Wayland, but this isn't an option for us. If I could get some guidance on which setting I'm missing it would be appreciated, I am having difficulty searching for a solution to this issue.
edit: This is on a Pi 5
-
@curieos Try to turn off screen blanking using
rpi-config. If that isn't what you're looking for, check out DPMS and if turning off DPMS or standby does what you you want (xset -dpmsorxset standby off).Duet software engineer
-
@chrishamm None of those commands do what I want. I specifically want the old behavior of screen blanking from Bullseye on Pi 4 back, where after a certain period of time the screen blanks (goes black) but the display doesn't turn off completely, and when it is tapped on it comes back after a moment without registering the tap that woke it up.
The closest I can get to this behavior is with screen blanking on, dpms enabled, the
soption on xset set toblank, and the monitor settings changed to not turn off when no signal is detected. I can tap on the display to bring it back up, but it takes longer since the display has to come out of standby, and it registers the tap that woke it up, which is quite dangerous.Maybe this is a Pi 5 behavior change, I'm not certain, but the problem is when the screen blanks the monitor stops detecting a signal and turns off. Wayland was only enabled for an afternoon while I was searching for a replacement on-screen keyboard, but I don't recall this being an issue there. I can't recall if the display ever blanked, but I know for a fact that it never turned off.
-
@chrishamm I dug into this a little bit by setting up a test machine with a Pi 4 and stock Bullseye image. Looks like it's set to disable DPMS, with blanking enabled in xset and rpi config, and a timeout/cycle of 0 in xset. I replicated these settings on the Bookworm machine and it still has the incorrect behavior. Looks like there's something else missing.
-
@curieos In that case try to turn off all energy saving options, install xscreensaver, and set that to blank the screen. That should do what you want.
-
@chrishamm Was xscreensaver installed on the older bullseye image? I'll give that a try when I get into work later, thanks!
