Raspberry Pi OS 12 (Bookworm) released

[TheOldPresbyope]

Congrats on scoring a Pi5 and, yep, they're speedier.

I was overthinking the local display issue. After whittling down the cruft I found on the InterWeb™, here's what seems to be a minimum setup for starting chromium-browser in a local display on Bookworm Lite:

Code:

# First, install the wayfire package if it's not present already
pi@raspberrypi:~ $ sudo apt install wayfire

#create the configuration file to look like the following
pi@raspberrypi:~ $ cat .config/wayfire.ini
[autostart]
chromium=chromium-browser https://moodeaudio.org \
--ozone-platform=wayland \
--enable-features="OverlayScrollbar" \
--no-first-run \
--noerrdialogs \
--disable-infobars \
--kiosk

# Simply start wayfire
pi@raspberrypi:~ $ wayfire

How easy is that?! The wayfire windows manager takes over the screen and starts chromium-browser full screen.

The wayfire.ini file can have oodles of configuration sections and options (see Configuration  and the example wayfire.ini).

My first attempt at screensaving failed but I sure it'll work when I get time to play some more (real life and all that).

It's interesting to capture the output of wayfire to a file and examine the actions as it, for example, figures out that it's HDMI port 1 which is active (HDMI-A-1) and that, after enumeration of capabilities, the display mode is set to 1920x1080 @ 60.000Hz.

I dunno what caused the long delay I reported previously. It hasn't happened again.


Regards,
Kent