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.
C cdebiandesktop-environmentebpffirewalllandlocklinuxlinux-distributionopen-sourceprivacyquickjsraspberry-pi-5reactsecuritywaylandwayland-compositor
Merge branch 'v082-inmut2' into v082-integration
Federico Pereirae39c0823070c
diff --cc CHANGELOG.mdindex 1813fbe,f41cd62..f5bfeee--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -54,86 -12,33 +54,113 @@@ of the matching [GitHub release](https:## [0.8.2] - Unreleased+### Added++- **Design study: an immutable LordOS with A/B system images** ([docs/IMMUTABLE.md](docs/IMMUTABLE.md)).+ It compares dm-verity system partitions, fs-verity, composefs, OSTree, A/B root partitions and+ btrfs snapshots against Debian 13, the Store, the Raspberry Pi 5 and LordOS's threat model, and+ recommends a separate, optional edition: a read-only `/usr` verified by dm-verity in two slots,+ one signed boot image per version, automatic fallback to the previous version when an update+ doesn't start, and `/etc` and the home folders kept on their own partition. The classic edition,+ `install.sh` and in-place updates stay as they are; there is no conversion of existing systems.+- **Experimental build of that design** (`tools/immutable/`, not part of the regular ISO or+ Raspberry Pi image): a disk image for UEFI virtual machines with the A/B layout, a signed+ update into the other slot, and a scripted demonstration in which a deliberately broken version+ fails three times and the machine returns to the previous version on its own. Its payload is a+ minimal Debian 13, not the LordOS desktop yet; the rest of the plan moves to later versions.+- **New wallpapers.** Eleven original LordOS wallpapers in three categories: **Signature** (Crystal+ Crown, Eternal Dawn, Royal Flow, Royal Waves, Violet Horizon), **Lumo** (Celestial, Aurora) and+ **Cosmos** (Event Horizon, Infinite Galaxy, Solar Odyssey, Stellar Voyage), created by iPERFEX+ with an AI image generator. Settings → Wallpaper now lists every wallpaper grouped by category,+ with the previous four gradients as "Gradients". They are installed once in+ `/usr/share/backgrounds/lordos/` as high-quality JPEG (about 4 MB in total) with small thumbnails+ for the pickers, and a higher-resolution version added later is used automatically on the+ screens that need it.++### Changed++- **New default wallpaper:** new users start on **Celestial**; anyone who already chose a wallpaper+ keeps it. The login screen (and the remote login page) now shows **Crystal Crown**.+- The Control Center shows the current wallpaper and three from the collection; the rest are in+ Settings → Wallpaper (**Change Wallpaper…**).+- **Suggested for your computer.** Store → Discover now starts with packages for the hardware+ LordOS finds in the computer, each with the reason it appears ("We detected a printer from HP+ connected by USB"): the guest tools of a VMware or QEMU virtual machine, the proprietary graphics+ driver for an NVIDIA card (labeled as not free software, never preselected, with what changes:+ DKMS, Secure Boot key enrollment, older cards, and that the free nouveau driver stays the+ default), vendor drivers for USB printers and scanners, driverless USB printing (`ipp-usb`),+ the Raspberry Pi 5's board tools, and the firmware package a Wi-Fi, Bluetooth, network or+ graphics device asked for and didn't find. One click shows the usual plan and installs through+ the package engine; "Don't suggest again" hides a card for good. When something new is+ suggested, the Store's Discover item shows a count and one notification says so. For a+ VirtualBox virtual machine the card explains that its guest utilities aren't part of Debian 13.+ Detection only reads the kernel's hardware files; nothing is sent anywhere. The rules are data+ (`assets/store/suggestions.json`); see [docs/PACKAGES.md](docs/PACKAGES.md).++### Fixed++- **Package lists after enabling a component.** Adding a component (such as `non-free-firmware`)+ or a source whose signed release file hadn't changed upstream left the package list as it was+ ("already up to date"); the index is now rebuilt whenever the set of lists it is built from+ changes.+- **Allow or block each destination inside Monitor's app rows.** Open an app in Monitor → Network+ and every name it reached (or address, when the system resolver gave no name) has its own+ allow/block switch, showing what the app's rules decide for it right now and why ("By the rule+ \*.example.com", "Follows this app's default", "Blocked by this app's restrictions"). A click+ writes, flips or removes the rule for exactly that name, the same rule Settings → Privacy →+ Network rules by app shows, and `lord-netperm` applies it at once. Long lists show eight and+ "N more…"; rows keep their place while the list is open+ ([docs/MONITOR.md](docs/MONITOR.md#per-destination-switches-082)).+- **Traffic history.** The Network tab's chart now zooms out from the live minute to 1 hour,+ 24 hours, 7 days and 30 days, steps back and forward one window at a time and has **Now**; with+ an app selected its own chart follows the same window, and the summary lists the apps that moved+ the most in it. Your session records bytes received and sent per minute (7 days) and per hour+ (30 days), for the computer and for each of your apps, in a small file in your home folder+ (`~/.local/state/lordos/net-history.bin`): never an address, a name or a country. Settings →+ Privacy → Monitor has **Keep a traffic history** (on) and **Clear History**+ ([docs/MONITOR.md](docs/MONITOR.md#traffic-history-082)).++### Changed++- **The map's moving dots cost about half as much.** lord-server now repaints several small+ rectangles per frame instead of the one box around every change, skips clipped parts of the+ interface outside them, and copies only those rectangles to the screen; the dots are small+ ready-made images. With Monitor's map animating, the animation's share of lord-server's CPU went+ from 2.9 to 1.6 points of one core (VM 119, CPU compositing), and every partial repaint of the+ desktop gets cheaper the same way. Blurred surfaces (the menu bar, the Dock) are still repainted+ whole when anything touches them, as in 0.8.1 ([docs/MONITOR.md](docs/MONITOR.md#082-several-damaged-rectangles-vm-119)).++### Not included++- **City names on the map.** Debian 13 only ships country-level IP databases (`geoip-database`) and+ LordOS's own is country-level too, so labels stay countries; no large download was added.+ ### Security++ - **Mail, Calendar, Contacts and Reminders run in their own sandboxed process.** Like Passwords+ and installed apps, each one is now `lord-server --app <id>` with Landlock, seccomp, no network+ and its own cgroup scope, instead of running inside the desktop's process. Mail's window can read+ only its own data folder; your files reach it only through the system's open/save dialog; it+ cannot open sockets, read the mail cache, the accounts file, `~/.ssh` or other apps' data (checked+ from inside the running process). They reach `lord-maild` only through `lord-server`, each with+ its own list of allowed requests (Calendar cannot read mail) and its own replies and events.+ Notifications, alarms, Dock quick actions, several windows and opening attachments keep working.+ Monitor shows each app as its own process with its name and icon, and the firewall's per-app+ restrictions (`lpk:mail`, …) apply to it ([docs/PRIVACY.md](docs/PRIVACY.md#system-apps-in-their-own-process-082)).++ ### Changed++ - Isolated apps start faster: the app host is compiled to bytecode once per session, so an app's+ JavaScript loads in ~23 ms instead of ~110 ms (Mail's window: ~145 ms from the click to its first+ frame on a 1.8 GHz test machine).+ - The Dock's quick actions and **New window** now work for the apps that run in their own process;+ Passwords stays a single window.+ - An isolated app's process is named after the app (`mail`), not `exe`, in `ps` and Monitor.++ ### Fixed++ - Isolated apps showed times in UTC instead of the local time zone.+ - Trusting a self-signed certificate for an SMTP server on port 465 pinned it as the IMAP server's,+ so sending kept failing.## [0.8.1-beta] - 2026-10-19diff --cc apps/monitor/index.jsxindex 1fddfb2,555c58c..749c601--- a/apps/monitor/index.jsx+++ b/apps/monitor/index.jsx@@@ -320,10 -318,48 +320,16 @@@ export function Cell({ col, children, c);}-function DisksTab({ s, last }) {- const t = useTheme();- const { t: tr } = useLocale();- const card = useCardStyle();- const cols = [- { key: 'name', label: tr('monitor.diskCol'), flex: 1 },- { key: 'dev', label: tr('monitor.device'), width: 110 },- { key: 'size', label: tr('monitor.size'), width: 100, num: true },- { key: 'read', label: tr('monitor.read'), width: 110, num: true },- { key: 'write', label: tr('monitor.write'), width: 110, num: true },- ];- return (- <>- <Card icon="disk" title={tr('monitor.allDisks')}>- <Pair items={[{ label: tr('monitor.read'), value: fmt.rate(tr, last.disk.read), color: C.read }, { label: tr('monitor.write'), value: fmt.rate(tr, last.disk.write), color: C.write }]} />- <Chart series={[{ label: tr('monitor.read'), values: s.read, color: C.read }, { label: tr('monitor.write'), values: s.write, color: C.write }]}- format={(v) => fmt.rate(tr, v)} times={s.times} height={150} bg={card.bg} />- </Card>- <Table cols={cols} rows={last.disk.disks.map((d, i) => (- <View key={d.name} style={{ flexDirection: 'row', height: 30, alignItems: 'center', paddingHorizontal: 10, backgroundColor: i % 2 ? t.hover : 'transparent' }}>- <Cell col={cols[0]}>{d.model || tr('monitor.diskUnknown')}</Cell>- <Cell col={cols[1]} color={t.textDim}>{`/dev/${d.name}`}</Cell>- <Cell col={cols[2]}>{fmt.mem(d.size)}</Cell>- <Cell col={cols[3]}>{fmt.rate(tr, d.read)}</Cell>- <Cell col={cols[4]}>{fmt.rate(tr, d.write)}</Cell>- </View>- ))} />- {!last.disk.disks.length && <Text style={{ fontSize: 12, color: t.textDim }}>{tr('monitor.noDisks')}</Text>}- </>- );-}-// ---- Processes ----+ // An isolated LordOS app (its own process and scope, "lpk:<id>"): a package or a built-in app such+ // as Mail or Passwords; the process is shown with the app's name and icon.+ export const isolatedAppOf = (item) => (typeof item?.app === 'string' && item.app.startsWith('lpk:') ? getApp(item.app.slice(4)) : null);+export function AppGlyph({ item, size = 16 }) {if (item.app === 'lordos') return <LordOSLogo size={size} />;+ const iso = isolatedAppOf(item);+ if (iso?.Icon) return <iso.Icon size={size} />;if (item.appIcon) return <Image src={item.appIcon} style={{ width: size, height: size, objectFit: 'contain' }} />;const Ico = iconFromFile(null, item.appName || item.name || '?');return <Ico size={size} />;diff --cc docs/VM-SETUP.mdindex d236a08,9dd3039..80437f5--- a/docs/VM-SETUP.md+++ b/docs/VM-SETUP.md@@@ -1143,83 -1143,27 +1143,107 @@@ folder `~/LordOS-monred`, installed int- The session language, theme and accent were changed for the screenshots and restored from`~/.config-lordos-backup-monred` afterwards.+## Step 29 — 0.8.2: immutable (A/B) prototype (VM 122 `lordos-sandbox`, October 19)++See `IMMUTABLE.md`, "The prototype". On VM 122 (172.17.0.56), in its own folder `~/LordOS-inmut3`+(only `tools/immutable/`) and the work folder `/var/tmp/lordos-immutable` (base tree, images,+throwaway test key). The test images boot in **QEMU inside the VM** (nested KVM, OVMF): the VM's own+disk, boot, network and LordOS installation were not touched.++- **Installed** (`apt-get install --no-install-recommends`): `debootstrap`, `systemd-repart`,+ `systemd-ukify`, `systemd-boot-efi`, `systemd-boot-tools`, `cryptsetup-bin`, `erofs-utils`,+ `qemu-system-x86`, `ovmf`, `gpg`, `gpg-agent`, `gpgv`, `libcryptsetup12`, `mtools`,+ `dosfstools` (and their dependencies). `systemd-boot` itself and dracut were installed only inside+ the image's chroot, never on the VM (dracut would replace the VM's initramfs-tools).+- **Run:** `sudo tools/immutable/build.sh all` and `sudo tools/immutable/demo.py` (as root: `lord`+ is not in the `kvm` group, and it was not added). The demo's HTTP server listens on port 8642+ only while it runs; QEMU uses user-mode networking.+- **Left behind:** the packages above and `/var/tmp/lordos-immutable` (~5 GB; delete it to free the+ space). Nothing else changed.+## Step 29 — New wallpapers (VM 123 `lordos-monitor`, October 19)++Tree in `~/LordOS-wp`, built there (`make -C server -j4`, `make -C server test`: 23 passed,+3 skipped). Nothing was installed with apt.++- **Deployment, temporary:** `/usr/local/lib/lordos` was copied to `lordos.wp123-bak`, the new+ `lord-server`, `lord-sessiond`, `lord-vault`, `lord-maild`, the themes and `assets/` were installed+ over it, and the collection went to `/usr/share/backgrounds/lordos` with the+ `assets/wallpapers` link, as the package does. Afterwards the backup was copied back, the files+ that only the new build had were removed (`diff -rq` against the backup: identical), and+ `/usr/share/backgrounds/lordos` was deleted.+- **New user:** `~/.config/lordos/settings.json` was replaced by `{"language": "en"}` for the+ screenshots (Celestial by default, then Crystal Crown and light mode chosen in Settings) and+ restored from its backup (`wallpaper: "sunset"` again).+- **Login screen:** the session from before the deploy was ended and `/run/lordos/autologin-done`+ removed to show the greeter and then autologin again; `/etc/lordos/session.conf` wasn't changed.+- **Screenshots** with `screendump` from the Proxmox host, the pointer with+ `lord-qmp-input.py 123 1280 800`. eth0 and the VM's network weren't touched.+## Step 29 — Disk temperatures and SMART with smartmontools (VM 119 `lordos-spot`, October 19)++See `MONITOR.md` ("Disk temperature and health") and `SYSTEM.md` ("SMART with smartmontools").++- **Deploy:** the `v082-disks` tree built in `~/LordOS-dt082`; only `lord-server`, the themes and+ `assets/locales` were installed in `/usr/lib/lordos`, after a backup+ (`/var/tmp/disktemp082-backup/lordos-before.tgz`), and put back from it afterwards.+- **Test user:** `disktest` ("Disk Test", in the `sudo` group, a test-only password), created so the+ login screen could be used without touching `lord`'s password; removed afterwards+ (`userdel -r disktest`).+- **`drivetemp`** was loaded by hand (`modprobe drivetemp`) to check that QEMU's SATA disk gets no+ sensor (it has neither SCT nor attribute 194); unloaded afterwards.+- **smartmontools** was installed twice from the Disks app's "Install smartmontools" (the package+ engine's `pkg-install`), as the feature does, and purged afterwards (`apt-get purge+ smartmontools`), so the next test starts from "not installed" again. Before that, the fixtures in+ `server/tests/smart/` were captured with a `smartctl` unpacked into `/tmp/smx` (`apt-get download`+ + `dpkg -x`, never installed).+- Nothing else changed: no Proxmox setting, no network setting.+## Step 29 — Monitor → Network: per-destination switches, traffic history, several damaged rectangles (VM 119 `lordos-spot`, October 19)++See `MONITOR.md` ("Per-destination switches", "Traffic history", "0.8.2: several damaged+rectangles"). On VM 119 (172.17.0.54), built in its own folders (`~/LordOS-monred`, plus+`~/LordOS-before` from `origin/main` and instrumented copies for the measurements), all deleted at+the end.++- **Installed:** `linux-perf` (`apt-get install --no-install-recommends linux-perf`), to find where+ `lord-server` spends CPU while the map animates (`perf record -g -t <main thread>`). It stays+ installed.+- **Deployed for the test, then restored:** `/usr/lib/lordos` (the session's `lord-server`, the+ theme bundles, `assets`, and for the per-app history `lord-netperm` from the same tree, since the+ installed one predates the 0.8.1 traffic accounting) was saved in `/var/backups/lordos-monred-bak`+ and put back at the end (file list and contents compared with `diff -r`; the backup was then+ deleted). `lord-netperm.service` was restarted with the original binary.+- **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the+ end) and `/run/lordos/autologin-done` removed before each `systemctl restart lordos`, to start a+ fresh session with each build. The language (English), Appearance mode and Reduce motion were+ changed for the screenshots and measurements, and `settings.json` and `firewall.json` were+ restored from a copy; the history file the test wrote (`~/.local/state/lordos`) was deleted. The+ VM ends at the login screen.+- **Traffic:** `curl --limit-rate 40k` loops to Debian mirrors in ten countries from the SSH+ session (stopped at the end), and Firefox ESR (already on the VM) opening a few sites and one+ download (`~/Downloads/ls-lR.gz`, deleted).+- **Screenshots** with `screendump` from the Proxmox host; pointer and keys with+ `lord-qmp-input.py 119 1280 800` and `qm monitor 119` `sendkey`.+- Nothing in the network configuration was touched (`eth0` keeps 172.17.0.54).+ ## Step 29 — Mail, Calendar, Contacts and Reminders in their own process (VM 118 `lordos-notes`, October 19)++ See `PRIVACY.md` ("System apps in their own process"). On VM 118 (172.17.0.53), tree in+ `~/LordOS-inmut2`, built there and installed into `/usr/local/lib/lordos` (`lord-server`,+ `lord-sessiond`, and `lord-maild` and `lord-vault`, which this VM's install didn't have, plus themes+ and assets) by `~/inst-inmut2-118.sh`; the previous tree was saved in+ `~/inmut2-backup-20261019/lordos` and put back at the end (files that only the new build added were+ removed, so `diff -r` against the backup is empty). Sessions were the autologin session of `lord`+ (`/run/lordos/autologin-done` removed, then `systemctl restart lordos`).++ - **Installed, tests only, then purged:** `dovecot-imapd` (with `dovecot-core`, `dovecot-sieve`,+ `libexttextcat-2.0-0`, `libexttextcat-data`, `libunwind8`), its service disabled before it ever+ ran (`policy-rc.d`), run by hand from `/tmp/dctest` on `127.0.0.1:1143/1993` with a throwaway+ self-signed certificate and one test user (`[email protected]`, test-only password); a Python SMTP+ sink on `127.0.0.1:2465` (a transient unit, nothing relayed). `gdb` (with `libdebuginfod1t64`,+ `libdebuginfod-common`, `libpython3.13`, `libipt2`, `libsource-highlight*`, `libbabeltrace1`) to+ call `open()`/`socket()` inside the sandboxed Mail process. All purged afterwards; `/tmp/dctest`+ and the `dovecot`/`dovenull` users are gone.+ - **Input:** a uinput tablet (`~/uinput-inmut2-118.py`, as a transient unit, now with right click)+ driven through `/run/uinput-inmut2`; screenshots with `screendump` from the Proxmox host.+ - **Undone at the end:** `~/.config/lordos/settings.json` (English UI and `debugTiming` for the+ tests) restored from the backup, the Mail restriction in `firewall.json` removed, and the test+ data deleted (`~/.config/lordos/mail`, `~/.local/share/lordos/mail`, the four apps'+ `appdata` folders, two files in `~/Documents`). Nothing in the network configuration was touched.diff --cc server/Makefileindex 0947e8a,65f74c0..e1b89c9--- a/server/Makefile+++ b/server/Makefile@@@ -48,12 -48,12 +48,12 @@@ QJS_OBJ := $(patsubst %,build/qjs/%.o,q# .lpk app isolation, permissions and signing (src/sec, see docs/PRIVACY.md and docs/SIGNING.md)# Monitor: metrics, connections and the country of an IP (src/monitor, see docs/MONITOR.md)-MON_SRC := src/monitor/mon.c src/monitor/conn.c src/monitor/procctl.c src/monitor/proc_admin.c src/monitor/mmdb.c src/monitor/map.c src/ui/js_monitor.c+MON_SRC := src/monitor/mon.c src/monitor/disktemp.c src/monitor/nethist.c src/monitor/netrec.c src/monitor/conn.c src/monitor/procctl.c src/monitor/proc_admin.c src/monitor/mmdb.c src/monitor/map.c src/ui/js_monitor.c# Media (src/media, docs/MEDIA.md): only the lord-server side. Only lord-media links FFmpeg.-MEDIA_SRC := src/media/media.c src/media/mview.c src/media/capture.c src/media/annot.c src/media/maudio.c src/media/mpulse.c src/media/proto.c src/ui/js_media.c+MEDIA_SRC := src/media/media.c src/media/hwdec.c src/media/mview.c src/media/capture.c src/media/annot.c src/media/maudio.c src/media/mpulse.c src/media/proto.c src/ui/js_media.c- SEC_SRC := src/sec/json.c src/sec/sign.c src/sec/pkgstate.c src/sec/perms.c src/sec/cgroup.c src/sec/sandbox.c src/sec/brokersrv.c src/sec/brokercam.c src/sec/brokerkr.c src/sec/restrict.c src/sec/appid.c src/sec/pwguard.c+ SEC_SRC := src/sec/json.c src/sec/sign.c src/sec/pkgstate.c src/sec/perms.c src/sec/cgroup.c src/sec/sandbox.c src/sec/brokersrv.c src/sec/brokercam.c src/sec/brokerkr.c src/sec/brokermail.c src/sec/restrict.c src/sec/appid.c src/sec/pwguard.c# App mode: lord-server --app <id> runs an .lpk app as an isolated Wayland client (src/app)- APP_SRC := src/app/appclient.c src/app/appspawn.c src/ui/js_broker.c src/ui/js_brokercam.c+ APP_SRC := src/app/appclient.c src/app/appspawn.c src/ui/js_broker.c src/ui/js_brokercam.c src/ui/js_brokermail.c src/app/apphost_bc.cSRC := src/main.c src/kms.c src/gpu/gpu.c src/input.c src/canvas.c src/admin.c src/install/install.c src/apps.c src/lpk.c src/fsops.c src/remote/mirror.c src/remote/remote_admin.c src/remote/ssh_admin.c src/users/users_admin.c src/users/homedirs.c src/keyboard.c src/keylag.c src/ime.c src/wl/wl.c \src/ui/node.c src/ui/style.c src/ui/layout.c src/ui/transform.c src/ui/text.c src/ui/image.c \src/ui/paint.c src/ui/js.c src/ui/js_sys.c src/ui/js_term.c src/ui/js_wasm.c src/wasm/wasm.c src/wasm/wasm_run.c src/ui/js_sound.c src/ui/js_net.c src/sound/snd.c src/sound/pulse.c src/ui/otf.c src/ui/fonts.c \