Skip to content

v0.4.3

Choose a tag to compare

@github-actions github-actions released this 11 Nov 01:13
· 39 commits to main since this release

v0.4.3 — one binary, one theme engine, no rofi

The session is now entirely LazyOS. The last rofi surfaces and the mako
notifier are retired: every menu, picker and window is a subcommand of
/usr/bin/lazyos, the notifications are drawn by lazyos-notify on a
layer-shell surface, the installer is a full-screen TUI wizard, and the theme
engine carries 16 palettes with a live picker that repaints the desktop.

What changed since v0.4.2

The framework is the session (specs 014, 017)

  • rofi is retired in full. The package left uis/sway/packages.list, and
    lib-rofi.sh, bar-pick and ~/.config/rofi/ are deleted. The ~55 keyboard
    shortcuts and the bar's panel actions did not change: each old name
    (rofi-files, rofi-power, bar-menu, …) is a symlink to /usr/bin/lazyos,
    which resolves a command from argv[0] or from the words after it. The
    command table is 52 rows, 50 installed names, and --help/--symlinks print
    the same table the checks read.
  • The final 10 interactive surfaces are native: network, places, clean,
    kill, download, layout, file actions, agents, translate and dictation. Each
    filters as you type with case folding, acts on an enum instead of a shell
    string, and offers headless query flags (--status, --dry-run, --rows,
    --languages) for waybar and scripts.
  • 13 theme surfaces are generated from theme.toml (foot, waybar, mako-free
    notifications, starship, btop, lazygit, nvim, fzf, swaylock, greeter, the sway
    wallpaper/frame drop-in and both GTK stylesheets), so a new palette is one
    TOML file and no code.

Notifications are LazyOS (spec 019)

  • lazyos-notify replaces mako. It owns
    org.freedesktop.Notifications on the session bus and draws antialiased,
    rounded cards with soft shadows on a layer-shell surface anchored top-right
    under the bar. Urgency borders and dots, action buttons, progress tracks and
    theme pictures are drawn with tiny-skia; the pointer is released when the
    stack is empty, so nothing is occluded.
  • History without a daemon to ask: cards are logged to
    $XDG_STATE_HOME/lazyos/notify/history.jsonl and read back by
    lazyos menu notify (Alt+Ctrl+N). Do-not-disturb is one file under
    $XDG_RUNTIME_DIR, and critical alerts still pass through.
  • The OSD is one HUD card: volume and brightness draw a single card with a
    level bar instead of a stack of toasts, and the theme's own icons.

The installer is a wizard (spec 018)

  • lazyos installer is a full-screen six-phase wizard: pre-flight (it
    refuses when the root filesystem is the eMMC it would overwrite),
    localization (searchable IANA timezones, locale, keyboard layout with a
    keypress test), account (POSIX-validated user, masked password, hostname),
    a visual ChromeOS GPT diagram with a confirmation that defaults to Cancel and
    unlocks only after the disk's name is typed, a TaskView with an overall gauge,
    six phases and a streaming log from a detached worker, and a completion
    screen. --check and --dry-run verify the safety rules and simulate the
    install without touching storage.

Themes: 16 palettes, a live picker, live terminals

  • Eight new Omarchy ports: Catppuccin Latte, Dracula, Flexoki Light,
    Hackerman, Lumon, Matte Black, Omacon and One Dark, next to the existing
    Solarized Dark, Catppuccin Mocha, Tokyo Night, Rose Pine, Nord, Gruvbox,
    Everforest and Kanagawa.
  • lazyos menu theme (Alt+Shift+C) is a dual-pane browser: the left pane
    filters and marks the active theme, the right pane renders a live preview
    (the 16 ANSI swatches, the semantic role pills, a simulated bar, card and
    prompt) and verifies WCAG contrast. w cycles wallpapers, p peeks at the
    desktop with the candidate palette and rolls back on Escape, Enter commits and
    reloads the session.
  • Running terminals follow the theme: the active palette is pushed to open
    foot windows through OSC sequences, so a theme change repaints the
    terminals that are already open.
  • Every theme has a generated wallpaper (gradient plus the wordmark, the
    accent in the mark), cached per theme, and the greeter and lock screen consume
    the same palette.

The local model is Qwen3.5-0.8B

  • lazyos-model (Alt+Ctrl+M) runs Qwen3.5-0.8B (weight-space
    programming, Q4_K_M, 517 MB) in a floating window: 17.3 tok/s generation
    and 92 tok/s prefill on the four Cortex-A76 cores, 1.2 GB RSS at 4k
    context, so it coexists with the browser. Weights are fetched and verified
    against a pinned SHA-256; they are never committed or built.

Fixes worth naming

  • Monospace queries resolve to text fonts again. Upstream's
    10-nerd-font-symbols.conf aliased 50+ monospace families to the
    DFSG-stripped symbol font, so web pages and code blocks rendered as tofu or
    blank lines; LazyOS removes the alias, ships fonts-liberation and installs
    its own monospace fallback. Terminals still name the symbol font explicitly.
  • Bluetooth discovery is asynchronous and scans on demand, so the panel
    opens at once and stops scanning when it closes.
  • Region capture, OCR, QR and the colour picker detach from the menu before
    slurp grabs the screen, so the floating window is gone from the shot.
  • The Developer menu resolves the profile and PATH, uses structured
    pickers for restore, and the busy notifications take their subcommands.
  • Wi-Fi scanning is cached, waybar's JSON escapes are fixed, and detached
    children no longer inherit LAZYOS_UI.
  • Test runs suppress desktop notifications.

Validation

The tree builds with scripts/build.sh on the card's own port: Linux 7.2.7,
swayfx 0.6 on scenefx 0.5, workstyle 0.8.2, debootstrap for forky, and the
kpart signed with the vboot developer keys — futility show answers
Body verification succeeded. The image, its xz, the root filesystem tarball
and the kpart are sanitized and asserted clean by scripts/lib-dist.sh, and
SHA256SUMS covers the four.

lazyos --version prints 0.4.3, the same string as the committed VERSION.
All 497 tests pass (cargo test --workspace), and cargo fmt --all --check
and cargo clippy --workspace --all-targets -- -D warnings are clean.

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, and on the card Alt+Space → Install LazyOS
(or lazyos installer) is the same call with the questions asked first.

What it does not carry

The artifact is sanitized and asserted clean by
scripts/lib-dist.sh: no Wi-Fi profiles (a released
image knows no network and asks for one), no SSH host keys and no machine-id
(both generated on first boot, so every installation has its own identity), no
OpenCode sign-in and no personal files beyond the session configuration this
repository ships.

Known limitations

  • lazyos-notify is resident for the session, because a notification
    daemon is what owns the bus name; it is the third agreed exception to the
    no-daemon rule, next to cliphist's watcher and workstyle, and it idles
    without redrawing when no card is up.
  • The night light cannot reach the external monitor. MT8192's second display
    path (OVL1→RDMA1→DPI) has no gamma block bound, so modetest -M mediatek -p
    lists GAMMA_LUT on the 1366x912 CRTC and nothing on the 1920x1080 one;
    wlsunset logs gamma control of output … failed and the monitor keeps its
    own colour temperature.
  • The camera portal is not implemented (there is no access backend), so a
    Flatpak application sees no camera while Firefox and other native programs
    work. This is a limitation, not a bug to wait on.
  • The three-finger tab swipes do nothing when Firefox runs on Xwayland
    (MOZ_ENABLE_WAYLAND=0): the criteria need an app_id, and an X11 window has
    none.
  • The profile archive does not carry OpenCode's sign-in (it lives in
    ~/.local/share/opencode/opencode.db with the session history), and a Firefox
    profile copied while the browser is open is each database at its last
    checkpoint.
  • Wayvnc is loopback-only and read-only: the way in is an ssh -L tunnel
    (lazyos menu vnc has the command on a row), and the menu's input is
    deliberately off.
  • The installer refuses to run from the disk it would overwrite, which is the
    correct answer when it is opened on the eMMC install; the installation is made
    from the microSD, which can always be selected again in the firmware menu. The
    copy cannot be stopped: killing rsync or mkfs leaves a disk that looks
    written and is not.
  • The image is 6 GiB (IMAGE_SIZE_MIB=6144), which leaves about 2 GiB in the
    root partition; a larger card keeps the space after p3 unused unless the
    tarball is written with scripts/write-sd.sh, which sizes p3 to the whole
    card. The tarball's /etc/fstab is the unconfigured one the build leaves
    behind.
  • Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
  • The battery gauge's chemistry and time-to-empty properties are upstream
    failures; waybar reads the capacity directly, which works.
  • There is no hardware video decoder, and Vulkan is not usable (PanVK answers
    Mali-G57 not supported); the session renders through EGL and Panfrost, and
    video is CPU work.

Upstream

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