notGMman
commented
11 months ago Aha.... Now it's working! Not by magic...
The single difference between the pi 4 devices and the pi 5, which was nagging me, was that the pi 4's are logged in using a second user account, whereas the pi 5 uses the renamed default "pi" account. When I checked "wayfire.ini" on the pi 4's it seems creating a new user omits a "core" line to define default plugins. I have then added a [idle] section which works, from which I conclude that wayfire infers plugins to load from the sections defined in the file WHEN THERE IS NO CORE LINE. On the pi 5, there was a "core" plugins line - but for whatever reason it omitted "idle" - and since the screen did not blank, I conclude that only those core plugins are loaded irrespective of the [idle] section. Adding "idle" to the line of core plugins works after a reboot.
So the solution looks like adding "idle" to the core plugins line as well as a suitable [idle] section in wayfire.ini.
Firstly, apologies if this is a duplicate. I've had a browse - this one is the only similar issue I see - https://github.com/raspberrypi/bookworm-feedback/issues/67
My issue is the same as the title of that one - automatic screen blanking is not working on my pi 5. I do have 2 Pi 4B's running Bookworm and Wayland - they both blank OK.
Raspberry PI 5 Official Raspberry PI power supply 64-bit RaspOS Bookworm updated 01 Jan 24 - 12.4_Kernel:6.1.0-rpi7-rpi-2712_1 Booted from 128 GB SD-card ASUS monitor
Blanking was switched on in raspi-config and then the following added to .config/wayland.ini for the logged in user:
[idle] dpms_timeout=60
The screen doesn't blank. I've tried various timeout periods. The monitor blanks for the other devices plugged in which over 5 years have been multiple pi 3 and 4 running Buster, Bullseye and Bookworm.
Having read through that earlier ticket - which was resolved for the OP on their pi400, I will add the following command works to turn off the screen, as does the "on":
wlr-randr --output HDMI-A-1 --off
The suggested change in that ticket to /boot/firmware/cmdline.txt makes no difference. But I don't think I'd expect it to be relevant since the screen doesn't so much as flicker - it appears that the GUI isn't trying to turn the screen off, perhaps.