Skip to content

LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.

0.8.4.1: release test (ISO.md, VM-SETUP step 45, UPDATES), Board firmware screenshots, changelog

Federico Pereirac92de9a78edc
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 505288b..72f9a40 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,8 +12,8 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
## [0.8.4.1-beta] - 2026-10-25
-An update of 0.8.4 for the Raspberry Pi 5: its bootloader from Settings, the browsers in the Pi image,
-and the Pi image itself, which 0.8.4 held back.
+An update of 0.8.4 for the Raspberry Pi 5: its bootloader from Settings, and a new Pi image with the
+HDMI fix, the browsers and the ISO's system packages (0.8.4 held its Pi image back).
### Added
@@ -53,6 +53,8 @@ and the Pi image itself, which 0.8.4 held back.
### Known issues and limitations
+- **The Raspberry Pi 5 image** of this version is added to the release once it has been checked on an
+ HDMI monitor; the package update above doesn't depend on it.
- **A Pi set up from the 0.8.3 image** has no network time client: if Store → Updates fails, set the
time in Settings → Date & Time first, then install `systemd-timesyncd` from the Store.
- **The bootloader release** (*Default* or *Latest*) is shown but not changed from Settings: it is
diff --git a/docs/ISO.md b/docs/ISO.md
index cf8ab53..41e3949 100644
--- a/docs/ISO.md
+++ b/docs/ISO.md
@@ -443,6 +443,53 @@ text was fixed (sha256 `daba6313…c8ec65`). That ISO has the same binaries; onl
With the final ISO, UEFI boot, the network, ❖L/Enter and the installer summary were repeated. Nothing
was installed in that repeat.
+## Release test (0.8.4.1 Beta, October 25)
+
+An update of 0.8.4 (no new ISO: the 0.8.4 ISO stays the current one). `lordos_0.8.4.1_amd64.deb` built
+on VM 116 (build `20261025.9796cda3`) and `lordos_0.8.4.1_arm64.deb` with the Raspberry Pi 5 image on
+the Pi itself, natively, in `build-img.sh`'s arm64 chroot (build `20261025.5adba3b7`; the two builds
+differ only in `tools/rpi/build-img.sh`), both `RELEASE=1` from a tree whose `code-manifest.json` was
+signed on the maintainer's machine; `lord-server --check-code`: verified, release build.
+`make -C server test`: 23 passed, 0 failed, 8 skipped on VM 116 and 21 passed, 0 failed, 11 skipped in
+the Pi's arm64 chroot (`settings-hw-test` 160/160 on both, with the new `rpi-eeprom-update` parser
+cases); the seven node suites pass on the maintainer's machine; 0 compiler warnings. Both `.deb`:
+lintian 0 errors (17 warnings, the known ones); both SBOMs validated with `pyspdxtools`.
+
+The image: `lordos-0.8.4.1-rpi5-arm64.img.xz`, 784 982 908 bytes, sha256
+`da398fc6ee1cad611a07e34399a018250ab403a525157aa50a52172293d0e0da`, signed into its own
+`SHA256SUMS`/`SHA256SUMS.sig` with the release key. Against 0.8.4's image: 533 → 749 MiB compressed,
+2 747 → 3 674 MiB raw (Chromium, Firefox ESR and the ISO's system packages); the system is 2.3 GB.
+
+| Check | Result |
+|---|---|
+| Image, read-only (loop device on the Pi): `config.txt` has `display_auto_detect`/`camera_auto_detect` (lines 15–16) **before** `dtoverlay=vc4-kms-v3d` (line 21); `lordos` 0.8.4.1 verified, release build; Chromium 156 and Firefox ESR 153 (Debian's) with `custom_chrome_frame` true, the GTK theme and `inTitlebar` 1; `systemd-timesyncd`, `cups`, `avahi-daemon`, `exfatprogs`, `ntfs-3g`, `power-profiles-daemon`, `gsettings-desktop-schemas`, `rpi-eeprom` 28.34-1 installed; `lord-doc`, `lord-media` and `lord-netperm` with its BPF programs in the package; `dpkg --audit` clean | pass |
+| Store → Updates on VM 120 (0.8.4 installed from its ISO, UEFI, user `rtester`, `lordos.sources` on `apt-staging`): "LordOS 0.8.4.1 is available" with the notes; the plan is `lordos` only (11 MB); Update → no migration → "Restart required" → Restart (the sheet with the open apps) → login screen → About "Version 0.8.4.1 · Beta", build `20261025.9796cda3`, **Verified**; `lordos`, `lord-netperm`, `lord-fand` active, 0 failed units; Settings has no Board firmware on a PC (search "firmware": no results) | pass |
+| `apt update && apt-get upgrade` (VM 120 back at the fresh 0.8.4): 27 s, `lordos` and a Debian update, nothing kept back, no migration, `settings.json` byte-identical, `/run/reboot-required.pkgs` = `lordos`; `apt install --reinstall lordos` runs no migration; after the restart 0 failed units | pass |
+| Staging repository: the 11 Raspberry Pi packages verified against Raspberry Pi's signed index and the pinned SHA-256s; only the arm64 index lists them; `apt-repo.sh verify staging` passes. On the Pi, `apt-get install -s rpi-eeprom` with only Debian and LordOS sources (Raspberry Pi's archive left out, empty dpkg status) resolves everything from `LordOS:stable` and Debian | pass |
+| Raspberry Pi 5 (test SD, 0.8.4 image with the `config.txt` fix by hand): `apt-get install lordos` from staging: 0.8.4.1 in 18 s, no migration, `sshd -t` clean, `lord-server --check-code` verified | pass |
+| Settings → Board firmware on the Pi (a test account over the LordOS remote desktop): "Update available", installed Tuesday, May 26, 2026, latest Friday, September 25, 2026, release Default; **Update** → "Update ready: restart to finish" with the note and **Restart…** (the session's Restart sheet); the board staged `pieeprom.upd`, `pieeprom.sig` and `recovery.bin` and wrote `/run/rpi-eeprom-update-pending` (no `flashrom`, no `rpieepromab`) | pass |
+| After the restart: `vcgencmd bootloader_version` 2026/09/25 (`1accd665…`, was 2026/05/26 `086b83e3…`), the staged files gone; the page says "Up to date", installed = latest = September 25, 2026 | pass |
+| Browsers on the Pi (installed on the test SD the same way as the image, defaults from `browser-defaults.sh`): Chromium 156 on Wayland with one bar and LordOS's traffic lights; Firefox ESR 153 with its own single bar; Settings → Displays → Video: "Automatic", this board can't decode VP9 or AV1 in hardware, so sites are asked for H.264 | pass |
+
+Found in this test:
+
+- **The first arm64 package was incomplete.** Built in `build-img.sh`'s arm64 chroot (0.8.4's was built
+ natively on the development SD), it had no `lord-doc`, no `lord-media` and no BPF programs in
+ `lord-netperm`: the chroot lacked Poppler, libarchive, FFmpeg and clang, and `make` leaves those
+ parts out silently. It was published to staging only, then replaced there (the CDN path
+ invalidated). `build-img.sh` now installs the ISO's build packages in the chroot, copies
+ `packaging/`, and refuses a package without `lord-doc`, `lord-media` or the BPF programs.
+- **The Pi image had no network time client** (`systemd-timesyncd`): the board starts months behind
+ and refuses every signed index ("not valid yet"); the test SD needed its clock set by hand. Added.
+- **Restart from a session that is not on the monitor** (here the remote desktop) shows the Restart
+ sheet, but `lord-sessiond` only accepts power requests from the session shown on the monitor, so
+ nothing happens after the countdown; the board was restarted with `systemctl reboot`. The same
+ holds for Store → Updates' Restart Now; to fix in a later version (`canPower()` should be false
+ there).
+- **The Store's package engine ignores `/etc/apt/preferences.d`**, so on the Pi image its "Update all"
+ would take Raspberry Pi's `+rpt` builds (Chromium, BlueZ…) over Debian's; `apt` follows the
+ priorities (release notes, Known issues).
+
## Release test (0.8.4 Beta, October 19–25)
`lordos-live-0.8.4-amd64.iso`, built from ca52be1 (build `20261025.ca52be13`; the `v0.8.4-beta` tag,
diff --git a/docs/SETTINGS.md b/docs/SETTINGS.md
index 0cc586f..c1427ce 100644
--- a/docs/SETTINGS.md
+++ b/docs/SETTINGS.md
@@ -234,6 +234,11 @@ the peer and reports `canChange`. Monitor has the same view read-only, with a hi
## Board firmware (Raspberry Pi 5)
+| | | |
+|---|---|---|
+| ![Update available](settings-board-firmware-available.png) | ![Update ready](settings-board-firmware-pending.png) | ![Up to date](settings-board-firmware-uptodate.png) |
+| An update is available | Updated: restart to finish | After the restart |
+
LordOS's own page for the bootloader in the board's EEPROM, instead of `raspi-config`. It is in the
sidebar only on a BCM2712 board (`lord.system.info().board === 'pi5'`, from the device tree's
`compatible` list: Raspberry Pi 5, Pi 500, Compute Module 5). It shows:
diff --git a/docs/UPDATES.md b/docs/UPDATES.md
index a4de8db..de2098d 100644
--- a/docs/UPDATES.md
+++ b/docs/UPDATES.md
@@ -269,6 +269,10 @@ for now.
## Release tests
+- **0.8.4.1 (2026-10-25):** 0.8.4 → 0.8.4.1 from the Store and with `apt` on VM 120 (no migration,
+ nothing kept back) and with `apt` on the Raspberry Pi 5; the Raspberry Pi packages of the new
+ `pool/rpi/` resolve on a Pi with only Debian and LordOS sources ([ISO.md](ISO.md), "Release test
+ (0.8.4.1 Beta)").
- **0.8.4 (2026-10-25):** 0.8.3 → 0.8.4 from the Store and with `apt` on VM 120, and with `apt` on the
Raspberry Pi 5: migration 005 only, the two new libraries (`libsrtp2-1`, `libusrsctp2`) installed
as dependencies, settings byte-identical; `apt-get upgrade` keeps `lordos` back (new
diff --git a/docs/VM-SETUP.md b/docs/VM-SETUP.md
index 5b68707..8a7a98a 100644
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@ -1590,3 +1590,26 @@ See `ISO.md`, "Release test (0.8.4 Beta, October 19–25)".
`/root/.config/lordos` it created); the first-run check used a loop device on a decompressed copy
of the image in `/var/tmp/r084-fr` (removed). Network, the `lordbasex` account and the SD
partitions untouched; the board was not reflashed.
+
+## Step 45 — 0.8.4.1 release test (VMs 116 and 120 and the Raspberry Pi, October 25)
+
+See `ISO.md`, "Release test (0.8.4.1 Beta, October 25)".
+
+- **VM 116:** started (it was stopped); the release tree in `~/LordOS-0841`, built and tested there;
+ the `.deb` and its SBOM in `/var/tmp/`. Nothing installed. Left stopped.
+- **VM 120:** a Proxmox snapshot `r0841pre` first; then a fresh 0.8.4 install from the 0.8.4 ISO
+ (test user `rtester`, `openssh-server`, a sudoers drop-in, `lordos.sources` on `apt-staging`) and
+ a snapshot `r0841base`; upgraded with the Store, then again with apt from `r0841base`. Rolled back
+ to `r0841pre` (the earlier "Test User" install, at the login screen; ISO and boot order as
+ before), both snapshots deleted, left stopped.
+- **Raspberry Pi 5 (172.17.0.24, the user's TEST SD with the 0.8.4 image):** clock set by hand
+ (the image had no time client), `debootstrap`, `xz-utils`, `curl`, `gpg`, `dosfstools`, `fdisk`,
+ `dpkg-dev`, `python3`, `dpkg-repack` and `file` installed for the native image build; the
+ installed LordOS kernels repacked with `dpkg-repack` into `/var/tmp/lordos-kernel/out` (`dpkg
+ --verify` clean first: the same files as the 0.8.4 image's). Tree in `/var/tmp/lordos-src-0841`,
+ image work folder `/var/tmp/lordos-rpi-v0841`. `lordos` 0.8.4 → 0.8.4.1 from staging (then the
+ source put back on the live repository). For the Settings test: a test-only account `rtest`
+ (sudo group) and the remote desktop turned on; both removed afterwards. Bootloader updated once
+ through Settings → Board firmware (2026/05/26 → 2026/09/25). Chromium and Firefox ESR installed
+ from Debian with the image's browser defaults, to check them (left installed). Network and
+ partitions untouched; the board was not reflashed.
diff --git a/docs/settings-board-firmware-available.png b/docs/settings-board-firmware-available.png
new file mode 100644
index 0000000..ce130bb
Binary files /dev/null and b/docs/settings-board-firmware-available.png differ
diff --git a/docs/settings-board-firmware-pending.png b/docs/settings-board-firmware-pending.png
new file mode 100644
index 0000000..24b237c
Binary files /dev/null and b/docs/settings-board-firmware-pending.png differ
diff --git a/docs/settings-board-firmware-uptodate.png b/docs/settings-board-firmware-uptodate.png
new file mode 100644
index 0000000..7f0213f
Binary files /dev/null and b/docs/settings-board-firmware-uptodate.png differ