Skip to content

v0.2.0 — the session release

Choose a tag to compare

@Brunux Brunux released this 21 Oct 22:23
· 324 commits to main since this release

v0.2.0 — the session release

The boot chain, the disk layout and the install/backup tools are the ones
v0.1.1 validated; what changed is everything above the compositor. The machine now
boots into a session with one picker instead of two, a file browser that draws the picture of what
it lists, a manual rendered in the terminal, capture and download menus, dictation, tablet mode,
and an idle screen that is a small animation instead of a still frame.

What changed since v0.1.1

  • The session runs on swayfx. Debian's plain sway cannot round a window's corners, draw a
    shadow under it or blur what is behind it. compositors/swayfx/ pins swayfx 0.6 (a fork of
    sway 1.12) on scenefx 0.5, and the packages keep sway's names, so sway, /etc/sway and apt
    all still work. Blur is on, with two measured paths: a tiled window samples a wallpaper that was
    blurred once (0.07-0.11 ms full screen on the Mali-G57), a floating one is re-blurred from what is
    behind it (2.1-2.2 ms full screen, only while visible). The numbers are in
    docs/optimization.md §7.
  • One picker: rofi 2.0 replaces tofi and fuzzel. $mod+d launches applications, $mod+Tab
    switches windows, $mod+Shift+d runs a command, and the bar's popups are rofi's dmenu. The theme
    is solarized, the launcher and window switcher show the real icons, and global-kb is on so a
    menu keeps the keyboard instead of the session's bindings acting behind it (verified: with it
    off, Alt+1 switched workspace instead of reaching the menu).
  • Files, in two shapes on purpose. Alt+Ctrl+F and the Search key open rofi-files: one
    directory per run, every row carrying a thumbnail or a mimetype icon from the small Nureb
    icon theme (219 names, generated by scripts/make-icons.sh), Enter opening it in the program that
    fits it - a document in papers, a picture in imv (with chafa's sixels as the fallback),
    a video in mpv, text in bat. Search+Shift opens pcmanfm for the window people
    expect, and a double click resolves through the same rules via nureb-view. Alt+Search is the
    same question in a terminal: fd streaming into fzf with a preview pane.
  • The menus are short-lived rofi scripts, each one process while it is open and nothing
    afterwards: capture (screenshots to a dated folder, annotation, OCR, QR, recording), download
    (yt-dlp, video or audio), search inside files (rg), clipboard history (cliphist), emoji, quick
    settings, notifications, places (mount a stick with udisks2, unmount it, or format a disk),
    power (lock, suspend, hibernate, log out, reboot, shut down, behind a confirmation), calculator,
    colour picker, DNS, packages, reminders, about, agents and the key view. Slow actions show a
    busy card with a bar spinner, and the spinner is also the stop button.
  • The idle screen is the LazyOS screen, and it loops. 150 s without input and the screen fills
    with the LAZYOS wordmark, :: lazy by design :: and » press any key to continue «, in
    solarized orange, one terminal-text effect rebuilding the letters after another. Any key ends it
    at once. It runs at 30 fps: a full cycle of the seven effects is 70 s of wall time and 8.5 s of
    CPU (about 12 % of one core), against 32 % for Deboma's 120 fps loop. This is the one surface
    that says LazyOS; the rest of the distribution still says Nureb until the rename lands.
  • The lock waits for the lock. Every lock entry point (the 300 s timer, Alt+Ctrl+L, the Lock
    key, the two suspend shortcuts, the bar and the power menu) now goes through
    ~/.config/bin/sway-lock, which uses swaylock's -R readiness line so before-sleep cannot
    return while the screen is still drawing, stops the idle screen first, refuses to stack a second
    surface, draws the session's own wallpaper on base03, and raises a critical notification if the
    lock never comes up. The suspend shortcuts lock before they sleep, and a lock that fails blocks
    the suspend.
  • Tablet mode folds: bindswitch starts wvkbd with the solarized colours and the
    mobile-international layout, turns the touchpad and the physical keyboard off (the folded keys
    are on the table), and runs a 1 Hz poller over the accelerometer that rotates the output. The
    rotation frame is calibrated on the unit (tablet-mode calibrate) because the panel's
    accelerometer is not aligned the way the first table assumed; the fold that produced that row is
    in reports/feedback-2026-10-21-batch.txt.
  • Dictation (Alt+Ctrl+X) records, normalises the level, transcribes with whisper.cpp and
    types the result; the model is fetched once and verified against a pinned SHA-256. Hibernate
    refuses unless there is a disk swap and resume= on the command line, and says which condition
    is missing. Agents starts Claude Code, Codex or another CLI in ~/Work, installs one with
    npm into ~/.local, and keeps per-account config directories.
  • The manual is rendered, not printed. rofi-learn opens the seven pages with glow in the
    solarized palette (a glamour style with truecolour values), and the same menu searches the
    machine's own man pages with apropos. Alt+Ctrl+K lists every binding, generated from the
    live configuration.
  • The kernel and the memory story changed. HZ 1000, schedutil, transparent_hugepage=madvise,
    LRU_GEN, and swap is a compressed zram device created by systemd-zram-generator (not
    zram-tools, which failed on every boot next to it); systemd-oomd handles the 4 GB machine
    under pressure. Audio goes through the MT8192 UCM BootSequence that alsa-utils drives, so the
    speaker is a real sink and not Dummy Output.
  • The fixes the cards found: the session gets its locale through pam_env, SSH host keys are
    generated on the first boot that lacks them, the backlight is writable by the video group, the
    Wi-Fi profiles are rebound to whatever the interface is called, night light uses 4000 K, a time
    zone change restarts the bar, and check-system.sh reports the outcome of the SCP firmware load
    rather than its first attempt.
  • The image carries this repository at ~/Dev/Nureb, the commit it was built from in
    /etc/debian-aarch64-revision, and check-system.sh installed as
    /usr/local/sbin/check-system.sh, because the scripts that install to the eMMC and rewrite the
    kernel partition are meant to run on the device.

Validation

The latest hardware report in reports/ is the 2026-10-21 card:
95 OK, 2 WARN, 0 FAIL. The two WARNs are upstream noise, not gaps: the sbs-8-000b fuel gauge
logs Unknown chemistry: OTC0 (Nura's own log carries the same lines) and reads correctly, and the
Wi-Fi is on the world regulatory domain until an access point provides a country.

The idle screen and the lock helper landed after that card was written. They were exercised on the
build host - the loop, the immediate dismissal, the centring and the static fallback under a pty -
and the rows that need the panel are the first ones in
docs/test-checklist.md: the 150 s screen, a key during an effect, the
300 s lock, and a suspend that lands on a locked screen.

Assets

asset what it is
google-asurada.img.xz 6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd
google-asurada-rootfs.tar.zst the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh
google-asurada.vmlinuz.kpart the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other
SHA256SUMS SHA-256 of the three assets
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsync

On the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt - user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real.
scripts/install-emmc.sh installs it to internal storage.

What it does not carry

The artifact is sanitized and asserted clean by scripts/lib-dist.sh,
because the build rootfs does carry the maintainer's state:

  • no Wi-Fi profiles - a released image knows no network and asks you for one;
  • no SSH host keys - generated on first boot, so every installation has its own;
  • no machine-id - systemd generates a fresh one on first boot;
  • no personal files: no notes, no keys, no shell history, no agent accounts or model files. What is
    in /home is the ported session configuration, which lives in this repository.

Known limitations

  • The image is 6 GiB. A larger card keeps the space after p3 unused; write the tarball with
    scripts/write-sd.sh to size p3 to the whole card.
  • The tarball's /etc/fstab is the unconfigured one the build leaves behind: write-sd.sh
    generates the real one.
  • Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
  • Battery percentage is the capacity reading only; the gauge's chemistry and time-to-empty
    properties are upstream failures, and waybar reads the capacity directly.
  • There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
    supported
    ), which is why the session renders through EGL and Panfrost and why video is CPU work.
  • The published Wi-Fi profile import is one-directional: scripts/wifi.sh import binds a saved
    profile to any interface, but a profile the image does not carry is entered at first login.

Upstream

Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5.