Repository navigation
v0.4.2
v0.4.2 — eight themes, generated wallpapers and a themed greeter
The session now has eight built-in themes, each with its own generated
wallpaper, and the greeter (tuigreet) and lock screen (swaylock) consume the
active theme — no code changes when a theme is added.
What changed since v0.4.1
-
Eight themes as pure data: Solarized Dark (default, brand), Catppuccin
Mocha, Tokyo Night, Rose Pine, Nord, Gruvbox, Everforest Dark and Kanagawa.
Each is atheme.tomlwith the 16 ANSI colours, the semantic roles
(background, text, accent, danger, …), an accent pair and a gradient pair.
Adding a theme is one TOML file — the generator (lazyos-theme) parses it,
derives missing roles, checks the contrast floor (4.5:1 fortext, 3:1 for
signal roles) and refuses the theme if it cannot be read. -
Generated wallpapers: Each theme gets a deterministic wallpaper at build
time — a vertical gradient from the theme's background to a slightly lighter
version, with the LazyOS wordmark centered. Thezof the mark uses the
theme's accent colour, the_cursor uses the orange (warn) accent. Wallpapers
are cached at~/.cache/lazyos/wallpapers/andtheme setgenerates them on
the first switch. The first wallpaper becomes the desktop background and the
lock screen image. -
Themed greeter: The greeter (Debian's tuigreet 0.9.1, which has no
--config
support) receives its colours through generated flags in
~/.config/lazyos/greeter. The wordmark is rendered in the theme's colours.
No code changes when a theme is added — the template is data. -
Themed lock screen: swaylock reads its colours from the theme palette
(ring colours for the indicator, text colours for the prompt, the wallpaper
from the theme's wallpaper list). The photograph (mountains.jpg) remains the
default lock image for the brand; themes provide their own wallpaper. -
Theme menu preview:
lazyos menu theme(Alt+Shift+T) renders a live
preview with a 128px sixel wallpaper thumbnail for the highlighted theme.
The thumbnail is generated alongside the full wallpaper and decoded once. -
Pure data theme engine: The engine owns every surface — foot, waybar,
mako, rofi, btop, lazygit, nvim, fzf, swaylock, the sway wallpaper and frame
drop-in, the greeter flags, starship — all generated from the single
theme.toml. Writes are atomic (<target>.newthen rename), idempotent (a
secondtheme setis a no-op), and a hand edit is reported not silently
overwritten (--forcereplaces it). -
Manual page updated:
04-software.md§ Themes documents the eight
themes, the wallpaper cache, the greeter and lock screen theming, and the
idempotent write rules. -
AGENTS.md bullet added: Documents the pure data theme engine and the
eight built-in themes.
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.
All tests pass: 450+ (cargo test --workspace), cargo fmt --all --check
clean, cargo clippy --workspace --all-targets -- -D warnings clean. Golden
fixture files updated for the greeter and swaylock surfaces across all eight
themes.
scripts/check-system.sh on the built image reports the new theme surfaces
(greeter, swaylock, wallpaper) as present and correct.
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=fsyncOn 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 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
- The night light cannot reach the external monitor. MT8192's second display path
(OVL1→RDMA1→DPI) has no gamma block bound, somodetest -M mediatek -plists
GAMMA_LUTon the 1366x912 CRTC and nothing on the 1920x1080 one;wlsunsetlogs
gamma control of output … failedand 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 anapp_id, and an X11 window has
none. - The profile archive does not carry OpenCode's sign-in (it lives in
~/.local/share/opencode/opencode.dbwith 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 -Ltunnel
(rofi-vnchas the command on a row), and the menu's input is deliberately
off. - Install LazyOS refuses to run from the disk it would overwrite, which is the
correct answer when the menu 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: killingrsyncormkfsleaves 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 afterp3unused unless the
tarball is written withscripts/write-sd.sh, which sizesp3to the whole
card. The tarball's/etc/fstabis 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.