I have a Pi 5 8GB running fully updated Bookworm that uses feh to display a permanent slideshow on a monitor. The Pi is not connected to a keyboard or a mouse. To save energy the Pi is connected to a PIR with a python script that blanks the screen when no motion is detected for 60 seconds and wakes up the screen when motion is detected. This sytem worked perfectly on Bullseye (with slightly different code to put the screen to sleep and wake it up), and initially worked on Bookworm with amended code listed below.
It uses the following python code snippets are used to sleep and wake the screen:This system worked OK until a recent update ... now when no motion is now detected the screen does go blank, but then immediately wakes up and displays a lock screen with username and password boxes to unlock. Screen Blanking is not enabled, Adding "vc4.force_hotplug=1" or "vc4.force_hotplug=2" to the end of "/boot/firmware/cmdline.txt" has no effect. Changing from a Benq to an Asus monitor has no effect.
I can probably get it to work using my orginal code designed for an X11 system but I would rather stick with Bookworm - since it has worked. Something seems to be waking the monitor up immediately after being put to sleep and stimulating a lock screen! I suspect the issue is to do with Wayland being updated.
Any suggestions how I can fix Wayland to enable normal operation? Thank you in advance.
It uses the following python code snippets are used to sleep and wake the screen:
Code:
'wlr-randr', '--output', 'HDMI-A-1', '--on''wlr-randr', '--output', 'HDMI-A-1', '--off'I can probably get it to work using my orginal code designed for an X11 system but I would rather stick with Bookworm - since it has worked. Something seems to be waking the monitor up immediately after being put to sleep and stimulating a lock screen! I suspect the issue is to do with Wayland being updated.
Any suggestions how I can fix Wayland to enable normal operation? Thank you in advance.
Statistics: Posted by SimonDuffy — Sun Feb 25, 2024 9:34 pm