application/pdf now opens in Evince when Evince is installed, and in Firefox until then. Evince is on
the curated list but the image doesn't install it: it's a Flatpak on the GNOME runtime, which nothing else
in the image uses, measured at about 290 MB of download and 650 MB on disk for a 13 MB app. A first-boot
unit that installed it for everyone was written and dropped over that cost. The handler chain lists both,
and xdg-mime skips a handler whose .desktop doesn't resolve, so a PDF opens without asking and the
chain never answers "no method available for printing this document". A native alternative was checked
against the pinned Buildroot tree before settling: its mupdf only builds X11/GLUT front ends on a Wayland
desktop, its poppler has no glib wrapper, and zathura isn't a package at all.
Firmware. The Desktop got a Firmware app and the machinery behind it: fwupd enabled, a check timer,
an offline-updates timer, an unprivileged polkit rule so any logged-in local user can read and apply
device updates, and a notification applet that tells you when something is updatable. fwupdmgr get-devices
answers "does this machine need a BIOS update", which is the kind of question that otherwise turns into a
vendor utility and a USB stick.
The dev box's tools weren't on the PATH. cargo, rustc and uv were installed in
/opt/pengyos-guest/dev/bin, but nothing put them on PATH in any shell, and the container's own
/etc/profile doesn't run in a distrobox, so a dev guest appeared not to have Rust. It showed up as a flat
"no compiler on this machine" from an agent working on a Server, while the same agent found cargo fine in
its own guest shell. /etc/profile.d is the one file both shells source, and it's now written in the guest
image with tests asserting that file exists in each of the three places that read it.
No shipping in one corner of this release, but an answer worth having: a written assessment of whether a PengyOS machine can stream SteamVR to a Quest 3S wirelessly. The software stack is viable; the machines in the house that could run it aren't running PengyOS; and the Wi-Fi is the hardest of the three problems. It's in the repo as a document instead of a half-built feature.