A Desktop NVIDIA machine rebooted with an installer stick still in a USB port and came up with the
graphical installer open, running as root. It could have offered that machine's second disk as a
install target. The test for "is this a live boot" was "does a PENGYOS-PAYLOAD partition
exist", and an installed machine with the stick plugged in has one too. The bug went back to the
earliest images. Live boot is now decided the way it actually is: the kernel line. Installed
systems always boot with pengyos.data=, so pengyos-live-installer requires its absence and
refuses to run on an installed system even if something starts it by hand. The Firefox first-run
setup had the same test inverted, skipping on an installed machine that had a stick in it. Checked
under QEMU with a stick built from this change: on its own it opens the installer (5/5 session
checks plus a screenshot); booted with pengyos.data= it logs the unmet condition and stays out of
the way.
Steam, added to the startup apps on a Desktop, complained at every login that the session must
provide DISPLAY, then started fine from the launcher a moment later. Autostart fired as soon as
WAYLAND_DISPLAY existed; cosmic-session exports DISPLAY about a second after that, and Steam
beat it by 0.27 s. It waits for DISPLAY now, up to 15 s, then starts the entries without it so a
session with no Xwayland still gets its startup apps. On the machine it was measured on, Steam
started 0.46 s after DISPLAY appeared, no dialog.
Small one from the new remote desktop: the TLS certificate fingerprint was wider than the window showing it, so you couldn't read the thing you're supposed to compare. It fits now.