Hey there
I know it's been a while since you asked this (and the link you posted seems to be broken) but from the tldr I seem to be currently facing the same issues with wayland/wayfire. Setting the idle plugin in wayfire.ini works for me in most cases:
However: I am running a webinterface with a chromium kiosk inside a docker container. When displaying the kiosk, the screensaver does not kick in. This might however be related to chromium kiosk having something like a "no suspend flag" set (like when you watch a youtube video, your browser prevents the screensaver from starting). I tried for two days and did not find out how to turn this off. Just thought I leave this here so you can investigate along this path if you are still facing the problem and you want to stay on wayland.
If you don't mind switching to X, I got the screensaver running on Raspberry OS just as I wanted. However, to make it work properly, I needed to downgrade from kernel version 6.6 to 6.1 (which apparently is a known bug?). Then you can just set up xinitrc with xset dpms a b c where a, b and c are the timeouts in second for suspend, standby and off mode (in that order).
Hope this is of use to you and wishing you all the best![:)]( "Smile")
I know it's been a while since you asked this (and the link you posted seems to be broken) but from the tldr I seem to be currently facing the same issues with wayland/wayfire. Setting the idle plugin in wayfire.ini works for me in most cases:
Code:
[idle]screensaver_timeout = 300dpms_timeout = 600If you don't mind switching to X, I got the screensaver running on Raspberry OS just as I wanted. However, to make it work properly, I needed to downgrade from kernel version 6.6 to 6.1 (which apparently is a known bug?). Then you can just set up xinitrc with xset dpms a b c where a, b and c are the timeouts in second for suspend, standby and off mode (in that order).
Hope this is of use to you and wishing you all the best
Statistics: Posted by bootpi_development — Wed Apr 03, 2024 8:34 am