Wayland Setup Troubles

[Cubius]

Following the great guide on thedigitalpictureframe.com on setting things up on a bookworm installation on a Pi 4 I've run into some Problems.

Similar to #339 all I get output to my screen is a cursor and blank black void. Running the start_picframe.sh script manually however throws a failed to connect to display error trying to run wlr-randr --output HDMI-A-1 --off or [...] --on and does pretty much nothing further.

Unfortunately the documentation on wlr-randr is ... rather lean. There's not much I am able to do with that error short of digging into the source, which is mostly beyond my ability to comprehend.

I assume part of the issue is due to the slightly unorthodox display I'm using - an LCD panel with a custom driver board straight outta China. Though the Pi4b has been handling that pretty well all things considered, recognizing the resolution and other settings correctly as far as I can tell. The Pi3b I'm looking to replace needed to be force fed some HDMI timings through /boot/config.txt just to be able to drive the panel at 4k.

[paddywwoof]

@Cubius sadly there doesn't seem to be anything to turn the monitor off and on in wayland. On my frame I'm just turning the brightness down to zero. Hopefully a better solution will be found...

[paddywwoof]

I think the wlr-randr lines can be taken out of the start_picframe.sh script, so try that to start with. Presumably you tried upgrading pi3d to the latest fixed version. If you can get normal desktop rendering on your monitor it ought to work with OpenGL rendering from pi3d and picframe. The blank screen with the cursor normally indicates that something has stopped picframe running. Try looking in the output of journalctl - go to the end with END, quit with Q. You might be able to find a python style error in there!