Raspberry Pi OS 12 (Bookworm) released

[TheOldPresbyope]

I forgot to post my final wayfire.ini file

Code:

# initialize wayfire and run chromium-browser in full-screen kiosk mode
[core]
# load only essential plugins; if none specified then all available
# core plugins are loaded (>20) - doesn't materially affect startup time
# but seems like good housekeeping
plugins = \
autostart \
idle
[autostart]
# some say following two settings speed up app loading but that's not
# been my experience with this desktop-less kiosk application -
# reference - default wayfire.ini configuration file and
# bbs.archlinux.org/viewtopic.php?267232
#import-enviroment = systemctl --user import-enviroment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
#dbusupdate = hash dbus-update-activation-environment 2>/dev/null && dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY
# start chromium-browser with usual options + wayland protocol ; give process an arbitrary name
chromium=chromium-browser https://moodeaudio.org \
--ozone-platform=wayland \
--enable-features="OverlayScrollbar" \
--no-first-run \
--noerrdialogs \
--disable-infobars \
--kiosk
[idle]
# blank screen after timeout
screensaver_timeout = 60
dpms_timeout = -1
# required for fullscreen kiosk
disable_on_fullscreen = false

Raking through copious debugging output I can see where the first run and second run differ. The discrepancies in elapsed time show up  in the bowels of stuff like wayfire code executing "Framebuffer Reset..." and GLES2 "Updating shadow. ... for linear texture..." and even then only once out of many such lines.

I'm trying to figure out where best to ask...prolly the wayfire wiki.That's for another day, though; for now, I'm content with a usable Bookworm kiosk.

Regards,
Kent