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
Docs audit (part 2): docs index lists every file, MONITOR up to 0.8.5, RASPBERRY HDMI since 0.8.4.1, real helper reply codes in NETWORK and PACKAGES, admin groups, protected paths, isolated system apps, Xwayland mentions, memory claim qualified
Federico Pereirabb9433a41c06
diff --git a/docs/DOCUMENTS.md b/docs/DOCUMENTS.mdindex dd38fa7..7a8919c 100644--- a/docs/DOCUMENTS.md+++ b/docs/DOCUMENTS.md@@ -62,7 +62,7 @@ In the style of a classic document viewer:- note 🗨 (a text at a point);- freehand ✎.- ❖Z undoes the last annotation. Everything is saved **as a copy**, "name (anotado).pdf" next to+ ❖Z undoes the last annotation. Everything is saved **as a copy**, "name (annotated).pdf" (the suffix in the interface language) next tothe original, with ❖S or File → Save a copy. The original is never touched.- **Forms:** text fields, checkboxes, radio buttons and lists are filled in place, and saved withthe copy.@@ -96,7 +96,7 @@ How it draws:- shows the progress in the status bar;- at the end it says how many files came out and how many were skipped for safety.- **Compress:** the selection goes to a `.zip` alongside: "name.zip" if it's a single item, or- "Archivo.zip". It handles recursive folders, symbolic links as links and UTF-8 names.+ "Archive.zip" (translated, `docs.archiveName`). It handles recursive folders, symbolic links as links and UTF-8 names.- **Formats read** by libarchive: zip, tar (gz, xz, zst, bz2, lzma, lz), 7z, cpio, iso, ar, rar(list and extract only, as libarchive allows) and standalone `.gz/.xz/.zst/.bz2`. It only writeszip.@@ -151,7 +151,7 @@ formats).| text and code | the first lines | — || font (`.ttf/.otf/.ttc`) | a sample in several sizes | FreeType in lord-doc || archive | file count, size and the first entries | — |-| audio and video | a frame or the cover, if the SDK has `media.poster` (the media agent); otherwise, the icon | media agent |+| audio and video | a frame or the cover through `media.poster` (`MEDIA.md`); without lord-media, the icon | lord-media || file inside an archive | the same, after extracting only that one to the cache | lord-doc |The arrows go to the next one; Space or Esc close it.@@ -325,5 +325,6 @@ server/build/doc-test server/build/lord-doc pdf file.pdf 900 # open, draw and- ZWJ sequences (❤️🔥, 👩💻) show as their parts, because the text engine doesn't join them yet;- in Linux apps it types by pasting, because there's no Wayland `text-input`.- **Untested:**- - Quick Preview of audio and video with `media.poster`: lord-media isn't built on VM 116;+ - Quick Preview of audio and video with `media.poster` was not measured here (VM 116 had no lord-media+ when this was written; `media.poster` exists now, `MEDIA.md`);- printing from Photos (it belongs to the media agent; the API is ready: `print.open({ image })`).diff --git a/docs/IMAGER.md b/docs/IMAGER.mdindex 2ae0f08..b6a2c2e 100644--- a/docs/IMAGER.md+++ b/docs/IMAGER.md@@ -338,8 +338,12 @@ The containers keep their own `node_modules` and cargo target folders in named v- **Not booted on a real Raspberry Pi:** the first-run file was applied with `--root` to the real0.8.3 image (arm64) from an amd64 build, and the image's own `firstboot` script runs `lordos-firstrun`- but wasn't executed (no board was reflashed, as asked). The next Pi image build ships- `lordos-firstrun`; images up to 0.8.3 ignore the file and start in setup mode.+ but wasn't executed (no board was reflashed, as asked). Since 0.8.4 the `lordos` package ships+ `lordos-firstrun`, so the Pi image published with 0.8.4.1 reads the file (a 0.8.4 image build+ applied a file from the Imager's writer with `--root/--boot`: 26/26, `ISO.md`, "Release test (0.8.4+ Beta, October 19–25)"); images up to 0.8.3+ ignore it and start in setup mode. A real first boot from a card the Imager prepared is still not+ recorded.- **Not tested with real drives:** only virtual ones (the USB gadget on VM 116, a disk image on thedevelopment machine). The authorized-open prompt of the Mac download, udisks2's `OpenDevice` withpolkit and the Windows download were not run against a real stick (the test opened its own diskdiff --git a/docs/IMMUTABLE.md b/docs/IMMUTABLE.mdindex 09ab82f..5379643 100644--- a/docs/IMMUTABLE.md+++ b/docs/IMMUTABLE.md@@ -50,7 +50,7 @@ experimental edition (PC, UEFI, full desktop, updates from the Store) is phase 1## Goals1. **A read-only, verified `/usr`.** Nothing at run time — not an app, not the user, not root — can- change a file of the operating system in a way that survives a reboot or goes unnoticed: every+ change a file of the system in a way that survives a reboot or goes unnoticed: everyblock is checked against a hash that the boot chain vouches for.2. **Atomic updates with automatic rollback.** An update is written next to the running system andbecomes active only by booting it. A power cut in the middle leaves the old system untouched. Adiff --git a/docs/LAYERS.md b/docs/LAYERS.mdindex cfedc30..2ee97ef 100644--- a/docs/LAYERS.md+++ b/docs/LAYERS.md@@ -75,7 +75,8 @@ import { Layer, Overlay, LAYERS } from '@lordos/sdk';`onClose` is called on a click outside (the anchor included toggles itself) and on Escape. Inthe desktop's process it goes to the `popover` layer, above the Dock and the other windows; aprotected window's list stays black in screenshots. In an isolated app's process (`.lpk`- apps and Passwords, `"process": "isolated"`) it goes to the window's own overlay host, above all+ apps and the system apps with `"process": "isolated"`: Passwords and, since 0.8.2, Mail, Calendar,+ Contacts and Reminders) it goes to the window's own overlay host, above allof the window's content (the app's surface is the window, so it can't leave it).- Used today by: the shell's menus, the SDK's `MenuButton`, the «fill from Passwords» button(`AutofillButton`), Settings' pop-up buttons and Passwords' pop-up menus. Calendar, Contacts anddiff --git a/docs/LORDOS-BRAND.md b/docs/LORDOS-BRAND.mdindex 9290006..5cbd895 100644--- a/docs/LORDOS-BRAND.md+++ b/docs/LORDOS-BRAND.md@@ -16,8 +16,8 @@ the renders by hand.LordOS is a free, fast and secure GNU/Linux distribution based on Debian, with a desktop environment ofits own, built from its fundamental components on top of Debian and Wayland. It has its own display server and Wayland compositor written in C and-its own React-based interface engine, the whole system idles at 465–487 MB of RAM-(`lord-server` 32–36 MB), and it brings a Dock, an app launcher, a menu bar, instant search and polished+its own React-based interface engine, the whole system idles at 465–487 MB of RAM (measured once,+live ISO and installed, in a VM; `lord-server` 32–36 MB RSS at idle; the paper's §7.1), and it brings a Dock, an app launcher, a menu bar, instant search and polishednative apps to PCs and to the Raspberry Pi 5, while still running regular Linux applications. Thecrown stands for a desktop where the user rules: fast, private and fully under their control.diff --git a/docs/MAIL.md b/docs/MAIL.mdindex b177e89..b19658a 100644--- a/docs/MAIL.md+++ b/docs/MAIL.md@@ -71,7 +71,8 @@ run in one sandboxed helper process, **`lord-maild`**.ranges behind v4-mapped, NAT64 and 6to4 addresses), checked on the address it actually connectsto (no DNS rebinding). Redirects (at most 3) go through the same check; each image is capped at5 MB and 20 s. Tested by `build/mailc-test`.-- **OpenSSL** is linked only by `lord-maild` and `lord-sessiond` (see `ARCHITECTURE.md`).+- **OpenSSL** is linked only by `lord-maild`, `lord-sessiond` and, since 0.8.5, `lord-fetch` (the blocklist+ downloader; see `ARCHITECTURE.md`).`lord-server` never links it.- **The compositor never waits**: requests are asynchronous (`lord.mail.poll()`), and inside`lord-maild` network work runs on account threads, never on the thread that reads the channel.diff --git a/docs/MONITOR.md b/docs/MONITOR.mdindex 5f4458f..1e151cf 100644--- a/docs/MONITOR.md+++ b/docs/MONITOR.md@@ -11,7 +11,11 @@ Phase 1 was read-only. Since then the Network tab holds per-app firewall rules (0.8.1, the Processes tab can stop a process and show its details ("Process actions"). In 0.8.2each destination of an app has its own allow/block switch, the traffic chart reaches back 30 days("Traffic history"), the Disks tab shows each disk's temperature and health, and the session can-notify when a disk gets too hot or less healthy ("Disk temperature and health").+notify when a disk gets too hot or less healthy ("Disk temperature and health"). In 0.8.3 the+remote desktop is a row of its own and blocking an app cuts the connections it had open. In 0.8.5+(in development) the Network tab becomes a tree with a view menu and search chips, LordOS's own+components and the system's services get rows of their own, and the menu bar network item and the+blocklists arrive ("Network, second generation").## Tabs@@ -23,6 +27,7 @@ notify when a disk gets too hot or less healthy ("Disk temperature and health").| Network | apps with connections, map, summary or detail of the chosen app (see below) || Disks | total read and write; one row per disk (model, `/dev`, size, temperature, health, rates); the chosen disk's temperature over the last 30 minutes and its health, with "Open in Disks" (see "Disk temperature and health") || Processes | sortable table (CPU, memory, threads, PID, user), search, "Mine" / "All"; Stop and Get Info for the selected process (see "Process actions") |+| Cooling | the cooling hardware drawn live, the active fan profile, a temperature and fan history and "full speed" (`apps/monitor/Cooling.jsx`, see `FANS.md`) |Charts pause with the mouse over them and show a crosshair with the values at that instant, as inTangoOS. Time always runs left to right, also in Arabic and Hebrew; the rest of the window mirrors@@ -115,7 +120,8 @@ the rest of the tab, and the first generation of the list.by app");- with a country chosen: bytes, apps and addresses (with ports and app).-Hosts are shown as IPs. There is no reverse DNS: asking for an IP's name sends it to the DNS+Hosts are shown by the name the system resolver gave the app (see "Per-destination switches"), or+as IPs when there is none. There is no reverse DNS: asking for an IP's name sends it to the DNSserver, and this app's rule is that no address leaves the machine.**"This computer"** is placed by the time zone (`/etc/localtime` → coordinates from@@ -204,7 +210,8 @@ Its panel:- the apps moving data now, with their rates;- **Recently denied** in the last ten minutes, with a count, the same destination grouped (×N);- the firewall mode: Allow silently, Deny silently, Off (`FIREWALL.md`, "The modes"). The ask mode- is not offered until it exists; rule profiles come with the rules manager (0.8.5);+ is not offered until it exists; rule profiles come with the rules manager (its own release after+ 0.8.5, `ROADMAP.md`);- the blocklists (lists on, entries) and "Open Monitor…".While the item is shown it reads `lord.monitor.netTotals()` (one read of `/proc/net/dev`) once@@ -298,7 +305,8 @@ edits (`FIREWALL.md`, "Rules by app"); there is no new enforcement:switch never moves under the pointer.- **What the switch shows** is what the app's rules decide for that destination right now:`sdk/fwrule.js` `decide()` runs the same order as `fw_decide` (restrictions, then the most- specific matching rule; no rule: the mode, which allows). When another rule decides, the row+ specific matching rule; no rule: the mode, which allows — since 0.8.5 the "Deny silently" mode and the+ blocklists can also decide, `decide()`'s `mode` and lists). When another rule decides, the rowsays which ("By the rule \*.example.com", "Follows this app's default"); a restriction ("nointernet") locks the switch and says so.- **What a click does** (`toggleOp()`): it writes the rule for exactly that name (or address),@@ -554,7 +562,10 @@ server/src/monitor/procctl.c the protected list, proc_signal() (pidfd) and the Gserver/src/monitor/proc_admin.c the root helper's proc-signal / proc-info (administrators)assets/monitor/ land.bin (Natural Earth 1:50m), geoip-country.mmdb.xz (DB-IP Lite)tools/gen-monitor-data.py generates that data, countries.js and the country names-tests/mmdb_test.c, tests/map_bench.c reader test and map benchmark+apps/monitor/RemoteDesktop.jsx (0.8.3) the remote desktop row and its detail+apps/monitor/Cooling.jsx the Cooling tab (lord.fan, see FANS.md)+apps/monitor/Firewall.jsx, FwRules.jsx, RuleSheet.jsx Settings → Privacy's firewall sections and the rule sheet+server/tests/mmdb_test.c, server/tests/map_bench.c reader test and map benchmark```### lord.monitor@@ -575,13 +586,14 @@ tests/mmdb_test.c, tests/map_bench.c reader test and map benchmark| `watchDisks(on)` | (0.8.2) with the Monitor closed, the thread wakes every 30 s and reads only the disk sensors || `diskTemps()` | (0.8.2) `{ t, disks: [{ name, model, rota, sensor, temp, tempT, tempMax, tempCrit, tempIdle, awake }] }` or `null` if nothing new; it does not keep the 4 Hz sampling alive |-Each disk in `sample().disk.disks` carries the same fields (`sensor`: `"nvme"`, `"drivetemp"` or-`null`; `temp` in °C or `null`; `tempT`: when it was read; `tempIdle`: a spinning disk at rest, not-read; `awake`: I/O in the last minute).| `history({ from, step, n, app })` | the traffic history in `n` buckets (see "Traffic history"), or `null` || `netTotals()` | (0.8.5) `{ t, rx, tx }`: the machine's byte counters now (every interface but `lo`), without the sampling thread (the menu bar item) || `historyEnable(on)` / `historyClear()` | the "Keep a traffic history" setting; deletes the history |+Each disk in `sample().disk.disks` carries the same fields (`sensor`: `"nvme"`, `"drivetemp"` or+`null`; `temp` in °C or `null`; `tempT`: when it was read; `tempIdle`: a spinning disk at rest, not+read; `awake`: I/O in the last minute).+No function takes paths or commands: the only arguments are booleans, a language code (letters,digits, `-` and `_`, up to 15), a PID with its start time (integers), `'TERM'` or `'KILL'`, and thehistory's integers and app id (`[A-Za-z0-9._:@+~/-]`, up to 127).@@ -606,8 +618,9 @@ history's integers and app id (`[A-Za-z0-9._:@+~/-]`, up to 127).### Connections`conn.c` does the same as `ss`: a `NETLINK_SOCK_DIAG` dump for TCP and UDP, IPv4 and IPv6, with-`INET_DIAG_INFO` (`tcpi_bytes_acked` and `tcpi_bytes_received` come from `tcp_info`). No root-needed. For other users' sockets, only how many there are is counted.+`INET_DIAG_INFO` (`tcpi_bytes_acked` and `tcpi_bytes_received` come from `tcp_info`). Since 0.8.5 it+also reads ICMP "ping", raw IP and packet sockets from `/proc/net/{icmp,icmp6,raw,raw6,packet}` (see+"Network" above). No root needed. For other users' sockets, only how many there are is counted.**Bytes per app (0.8.1).** `tcp_info` only exists for TCP and only while the socket is open, so upto 0.8.0 UDP — and with it QUIC: HTTP/3, a browser playing a video — counted nothing, and a closed@@ -702,12 +715,14 @@ With `Uint32Array` it costs one pixel per write.## PrivacySettings → Privacy → **Monitor** (registered with `registerPrivacySection` if the page exists) has-three switches, saved in `settings.monitor`, and a button:+four switches, saved in `settings.monitor`, and a button:- `connections`: see each app's connections. When off, the thread doesn't query sock_diag.- `geo`: place them on the map. When off, the country database isn't loaded.- `history` (0.8.2, on by default): keep the traffic history (bytes per minute and per hour, neveraddresses; see "Traffic history"). **Clear History** deletes it.+- `menuItem` (0.8.5, off by default): the network activity item in the menu bar (see "The menu bar+ network item").## Phase 2@@ -724,6 +739,11 @@ three switches, saved in `settings.monitor`, and a button:the system resolver returned; an app with its own encrypted DNS is held only by address rules.Screenshots: [light](firewall-domain-rules-monitor-light.png),[dark](firewall-domain-rules-monitor-dark.png).+- **Host names** without asking anyone (0.8.2): `lord-netperm` learns them from the system resolver+ and its notices carry them (`hosts`); the destinations are listed by those names.+- (0.8.2) Each destination's own switch and the traffic history; (0.8.3) blocking cuts the open+ connections; (0.8.5) the tree, the "Deny silently" mode, the blocklists and LordOS's own components+ as rows of their own (see "Network, second generation").**Planned:**@@ -731,9 +751,6 @@ three switches, saved in `settings.monitor`, and a button:- **Connection alerts** (the "ask" mode, `FIREWALL.md`) and rules per country.- **Devices:** `monitor.deviceUsers()` → `[{ kind: 'camera' | 'microphone', app, name, pid }]` andthe `monitorDevices` store (already exported, empty).-- **Host names** without asking anyone: `lord-netperm` already learns them from the system- resolver; its notices don't carry them to the session yet. The Network tab shows a `host` /- `hosts` field as soon as a notice brings one.- Usage alerts (the history is in place since 0.8.2).## Measurementsdiff --git a/docs/NETWORK.md b/docs/NETWORK.mdindex 7a881ed..edc6878 100644--- a/docs/NETWORK.md+++ b/docs/NETWORK.md@@ -52,10 +52,10 @@ lord-server --user ana ── lord-admin ──┘ net-* actions are forwardedlogs in.- **Sessions** bring nothing up. Each session's helper connects to `/run/lordos/netd.sock`(`SO_PEERCRED`: uid 0 only), introduces itself with `HELLO <user>` and forwards every `net-*`- action as it is. `lord-netd` works out again whether that user is an administrator (group sudo)+ action as it is. `lord-netd` works out again whether that user is an administrator (groups sudo, admin or wheel)and applies `A_ANYONE` as before. Replies go back to the helper that asked; events(`net dhcp…`, `net wifi…`, `net vpn…`) go to every session. Settings → Network didn't change.-- **A session's `net-restore`** answers `OK 0 interfaz(es): la red es del sistema (lord-netd)`.+- **A session's `net-restore`** answers `OK net.restoreSystem` ("The network is managed by the system").- **Wi-Fi and VPN passwords** stay in `/etc/lordos/net/wifi` and `/etc/lordos/net/vpn` (root, 0600).They travel over the socket between two root processes and never go back to a session.- **If `lord-netd` exits,** `lord-sessiond` starts it again: it waits 1, 2, 4… up to 30 s, and goes@@ -71,8 +71,8 @@ lord-server --user ana ── lord-admin ──┘ net-* actions are forwarded`/run/lordos/netd.lock` (`flock`) prevents two from running.- **Sessions reconnect:** when `lord-netd` restarts, each session's helper sees it come back withinotify on `/run/lordos` (the socket is created under another name and renamed once it listens)- and reconnects. An action in progress answers "la red del sistema se reinició: probá de nuevo"- ("the system network restarted: try again").+ and reconnects. An action in progress answers `ERR netd.restarted` ("The system network service+ restarted; try again").- **Without `lord-sessiond`** (a standalone `lord-server`, in development) there is no`/run/lordos/netd.enabled`, and the session's helper runs the network itself, as before (with`net-owner`). With that mark, a session never brings the network up on its own.@@ -170,27 +170,30 @@ Field values:## Actions (`admin.run('net-…', arg)`)The argument can have several lines (`\n`). "Anyone" means you don't need to be an administrator, as in NetworkManager.+Replies are code lines, never prose (`server/src/admin.h`, `errcode.h`): `OK <code> key=value…` or+`ERR <code> …`, which the UI translates with `t('status.<code>')` and `t('errors.<code>')`; a few+replies carry only data (a count, a public key).| Action | Argument | Who | Response ||---|---|---|---|-| `net-restore` | — | anyone | With `lord-netd`, it runs it by itself at boot; the one each session sends answers `OK 0 … la red es del sistema`. Without `lord-netd` (development) the first session applies it, noted in `/run/lordos/net-owner` while alive. It applies the configs in `/etc/lordos/net/if`, and free physical interfaces without a config go through DHCP (with Wi-Fi: wpa_supplicant plus the saved networks). `OK <n>` |+| `net-restore` | — | anyone | With `lord-netd`, it runs it by itself at boot; the one each session sends answers `OK net.restoreSystem`. Without `lord-netd` (development) the first session applies it, noted in `/run/lordos/net-owner` while alive. It applies the configs in `/etc/lordos/net/if`, and free physical interfaces without a config go through DHCP (with Wi-Fi: wpa_supplicant plus the saved networks). `OK net.restored count=<n>` || `net-up` / `net-down` | `if` | admin | `net-down` also stops its DHCP/wpa || `net-config` | `if\nmethod=dhcp\|static\|off\naddress=ip/n\n…gateway=ip\ndns=ip…` | admin | Saves and applies. Rejects system interfaces. || `net-manage` / `net-unmanage` | `if` | admin | Writes and deletes `/etc/systemd/network/00-lordos-<if>.network` (`Unmanaged=yes`) and runs `networkctl reload`. || `net-wifi-scan` | `if` | anyone | One `LOG` per network with `{ ssid, bssid, freq, signal, security: open\|wep\|wpa\|wpa2\|wpa2/wpa3\|wpa3\|enterprise, known }`, then `OK <n>` (≈3–10 s) |-| `net-wifi-connect` | `if\nssid\npassword` (empty if open) | anyone | `OK conectando…`. The result arrives as an EVENT. |+| `net-wifi-connect` | `if\nssid\npassword` (empty if open) | anyone | `OK wifi.connecting ssid=<ssid>`. The result arrives as an EVENT. || `net-wifi-disconnect` | `if` | anyone | || `net-wifi-forget` | `ssid` | admin | |-| `net-vpn-import` | `type\nname\nconfig`, type `wireguard\|openvpn\|ipsec\|pptp\|openconnect\|fortinet` | admin | WireGuard: `OK <public key>`; with `PrivateKey = generate` it creates it. The others: `OK importada`. For OpenVPN, first `lord.net.prepareOvpn`. The formats are below. If the program is missing: `ERR falta el programa de <tipo>…` |-| `net-vpn-enable` | `openconnect\|fortinet` | admin | Installs `openconnect` or `openfortivpn` with LordOS's package engine (the same as `pkg-install`): `LOG progress …` and `OK n instalado(s)…`. If it was already there: `OK ya estaba instalado`. |+| `net-vpn-import` | `type\nname\nconfig`, type `wireguard\|openvpn\|ipsec\|pptp\|openconnect\|fortinet` | admin | WireGuard: `OK <public key>`; with `PrivateKey = generate` it creates it. The others: `OK vpn.imported`. For OpenVPN, first `lord.net.prepareOvpn`. The formats are below. If the program is missing: `ERR vpn.missingProgram type=<type> package=<package>` |+| `net-vpn-enable` | `openconnect\|fortinet` | admin | Installs `openconnect` or `openfortivpn` with LordOS's package engine (the same as `pkg-install`): `LOG progress …` and the package engine's `OK`. If it was already there: `OK vpn.alreadyInstalled`. || `net-vpn-credentials` | `name\nuser\npassword` | admin | OpenVPN only. Stored with mode 0600. |-| `net-vpn-up` / `net-vpn-down` | `name` | anyone | WireGuard: `OK conectada`. OpenVPN: `OK conectando` and then an EVENT. |+| `net-vpn-up` / `net-vpn-down` | `name` | anyone | WireGuard: `OK vpn.connected`. The others: `OK vpn.connecting` and then an EVENT. || `net-vpn-delete` | `name` | admin | || `net-vpn-status` | `name` or empty | anyone | One `LOG` per VPN and then `OK <n>`:<br>`{ name, type:'wireguard', ifname, active, peers: [{ publicKey, endpoint, lastHandshake (unix), rxBytes, txBytes }] }`<br>`{ name, type:'openvpn', ifname, running, active }`<br>`{ name, type:'ipsec'\|'pptp'\|'openconnect'\|'fortinet', ifname, running, active, address }` |VPN names accept `[A-Za-z0-9_-]`, up to 24 characters. The interface, lowercased and trimmed to 15 characters, is `wg-`, `ovpn-`, `ips-`, `ppp-`, `oc-` or `fvpn-` + the name.-For every type other than WireGuard, `net-vpn-up` answers `OK conectando` and the result arrives as an EVENT. Only one IPsec can be connected at a time, because charon uses `/run/charon.pid`; the second one answers `ERR ya hay otra VPN IPsec conectada` ("another IPsec VPN is already connected").+For every type other than WireGuard, `net-vpn-up` answers `OK vpn.connecting` and the result arrives as an EVENT. Only one IPsec can be connected at a time, because charon uses `/run/charon.pid`; the second one answers `ERR vpn.ipsecBusy` ("Another IPsec VPN is already connected").### Import formats (IPsec, PPTP, OpenConnect, Fortinet)diff --git a/docs/PACKAGES.md b/docs/PACKAGES.mdindex 98cbcc5..c93bbfd 100644--- a/docs/PACKAGES.md+++ b/docs/PACKAGES.md@@ -98,7 +98,7 @@ All of them run in a separate process (`A_FORK`) and require an administrator us- Recommended packages are not installed by default. `--recommends` adds them, and if one of themcan't be installed it doesn't stop the rest.- If a request forces removing something that wasn't asked for, the action fails with- `ERR también hay que quitar: a, b` ("these must also be removed"). For example:+ `ERR pkg.removeAlso names=a,b` ("these must also be removed"). For example:- installing `postfix` removes `exim4`, because they are two mail programs and can't coexist;- removing a library removes what depends on it.@@ -120,10 +120,11 @@ LOG plan held libfoo (upgrades that can't be doneLOG plan total 4034148 24981 (bytes to download, KB the installed size changes by)LOG progress download 1048576 4034148 (phases: lists, index, download, unpack, configure, remove)LOG Unpacking featherpad (1.6.1-1) ... (everything else: text for the log)-OK 3 instalado(s), 0 actualizado(s), 0 quitado(s)+OK pkg.done installed=3 upgraded=0 removed=0```-(The final `OK` line is the helper's literal output: 3 installed, 0 upgraded, 0 removed.)+(The final `OK` line is a code line, as every helper reply: the UI shows it translated, "3 installed,+0 upgraded, 0 removed".)The `progress <phase> <done> <total>` lines are for a progress bar.@@ -179,14 +180,14 @@ needs `contrib` as well as `non-free`), is never offered as installable.| Detected | How | Suggests | Notes ||---|---|---|---|-| VMware virtual machine | DMI `sys_vendor` "VMware, Inc." or a PCI device of vendor `15ad` | `open-vm-tools` | Preinstalled since 0.8.1, so it normally shows as installed. `open-vm-tools-desktop` is not suggested: it targets X11 (clipboard and resize will come when LordOS supports them) |+| VMware virtual machine | DMI `sys_vendor` "VMware, Inc." or a PCI device of vendor `15ad` | `open-vm-tools` | Preinstalled since 0.8.1, so it normally shows as installed. `open-vm-tools-desktop` is not suggested: it targets an X11 session (LordOS runs X11 apps through Xwayland since 0.8.3, but its clipboard and resize integration was not tested there) || QEMU/KVM guest with a guest agent channel | a virtio port named `org.qemu.guest_agent.0` (only present when the host enabled the agent) | `qemu-guest-agent` | Clean shutdown from the host, frozen disks for backups, the guest's address || VirtualBox virtual machine | DMI product "VirtualBox" or PCI `80ee:cafe` | `virtualbox-guest-utils` | **Not in Debian 13** (main, contrib or backports): the card explains that, and that the kernel already has the guest drivers (display with VMSVGA, shared folders) || NVIDIA graphics card (x86_64) | PCI vendor `10de`, class `0300`/`0302`/`0380` | `linux-headers-amd64`, `nvidia-driver`, `firmware-misc-nonfree` | **non-free**. The card says the free `nouveau` driver is in use and stays the default; what changes: DKMS builds the module for each kernel, Secure Boot needs its key enrolled at the next restart, cards older than about 2014 need the free driver, and the LordOS desktop hasn't been tested with this driver yet. `nvidia-driver` also depends on packages in `contrib` (`nvidia-installer-cleanup`): without both components in the sources the card explains that instead (the LordOS ISO enables both) || USB printer | an interface of class `07`, by USB vendor ID: HP `03f0` → `hplip`, Epson `04b8` → `printer-driver-escpr`, Brother `04f9` → `printer-driver-brlaser`, Samsung `04e8` → `printer-driver-splix`, Canon `04a9` → `printer-driver-gutenprint` | the vendor's Debian driver | Vendors not in the table get nothing: most printers work driverless with CUPS || USB printer with IPP over USB | interface `07/01/04` | `ipp-usb` | Driverless printing and scanning: the device shows up like a network printer || USB scanner | udev's `libsane_matched=yes` for the device (`/run/udev/data/c189:N`; needs libsane's udev rules installed), by vendor: HP → `libsane-hpaio` | the vendor's SANE backend | Other vendors' backends are already in `libsane1` |-| Raspberry Pi 5 (and 500, CM5) | device tree `compatible` | `rpi-eeprom`, `raspi-utils`, `gpiod` (those that exist) | `rpi-eeprom` and `raspi-utils` come from the Raspberry Pi archive the LordOS image configures; `gpiod` from Debian |+| Raspberry Pi 5 (and 500, CM5) | device tree `compatible` | `rpi-eeprom`, `raspi-utils`, `gpiod` (those that exist) | `rpi-eeprom` and `raspi-utils` come from the Raspberry Pi archive the LordOS image configures, and since 0.8.4.1 also from the LordOS repository (`UPDATES.md`, "Raspberry Pi firmware packages"); `gpiod` from Debian || A device that asked for missing firmware | the firmware loader's "Direct firmware load for X failed" / "firmware: failed to load X" lines in the kernel log, minus files present now | the package that ships X (`iwlwifi-*`, `intel/ibt-*` → `firmware-iwlwifi`; `rtl_bt/`, `rtw88/`, `rtw89/`, `rtlwifi/`, `rtl_nic/` → `firmware-realtek`; `ath*k/`, `ar3k/`, `qca/`, `htc_*` → `firmware-atheros`; `brcm/brcmfmac*` → `firmware-brcm80211`; `brcm/BCM*` → `bluez-firmware`; `mediatek/`, `mt76*` → `firmware-mediatek`; `mrvl/`, `libertas/` → `firmware-libertas`; `amdgpu/`, `radeon/` → `firmware-amd-graphics`; `i915/`, `xe/` → `firmware-intel-graphics`; `nvidia/` → `firmware-nvidia-graphics`) | **non-free-firmware**, one card per package (Wi-Fi, Bluetooth, network adapter, graphics). The prefixes were checked against trixie's `non-free-firmware` Contents. If the package is installed and a file is still missing, nothing is offered. Files no prefix matches (e.g. `regulatory.db`, which a VM without Wi-Fi also asks for) get no card |Cards are ordered: installable, then explained (not available), then installed.diff --git a/docs/RASPBERRY.md b/docs/RASPBERRY.mdindex 7dcadec..7be4f02 100644--- a/docs/RASPBERRY.md+++ b/docs/RASPBERRY.md@@ -25,6 +25,14 @@ This document gathers what's needed to build the image, write it, develop on the> previous one stays installed and bootable (see "Switching kernels on a board"). Cross-compiled on> VM 116, installed on the Pi 5 and verified there: `verify-board`, the firewall cut test (15/15,> TCP and QUIC closed in 0.04–0.37 s) and `make -C server test`.+>+> **Update (2026-10-25, 0.8.4.1):** the Pi 5 image shows the login screen and the desktop on an HDMI+> monitor from the first boot (the display driver line in `config.txt` now comes after+> `display_auto_detect`/`camera_auto_detect`, plus 0.8.4's longer wait for the display driver;+> `CHANGELOG.md`, 0.8.4.1, Fixed). The image also brings Chromium, Firefox ESR and the ISO's system+> packages, and the bootloader is updated from Settings → Board firmware. A monitor plugged in after+> boot is followed from 0.8.5 (in development). **Still not measured:** frame rates and GPU composition+> timings on a monitor (checklist item 5), two monitors and 4K.## Models@@ -65,7 +73,7 @@ SD card or an NVMe, and the same image boots on the Pi 5 and the Pi 4.`custom_chrome_frame` and the GTK theme, Firefox's `/etc/firefox-esr/lordos.js` (`inTitlebar` 1),so both draw a single bar with LordOS's window buttons; the GTK themes, the video extension andthe video settings (`video-optimize`, Settings → Displays → Video) come with the lordos package.- Measured cost in "Release test (0.8.4.1 Beta)".+ Measured cost in `ISO.md`, "Release test (0.8.4.1 Beta, October 25)".- **The LordOS build of the Raspberry Pi kernel** (see "The LordOS kernel"), when`tools/rpi/build-kernel.sh` has built it; otherwise Raspberry Pi's archive kernel, with a loudwarning (it has no Landlock, BPF LSM or BTF):@@ -799,7 +807,8 @@ the per-app firewall was off on the Pi; `build-img.sh` enables it now. **The LorBPF LSM** (`CONFIG_BPF_LSM` is not set, and no BTF), so "No Bluetooth" for Linux apps isn't enforcedon the Pi (`lord-netperm` reports `"bluetooth":false`); the network and device programs work. Turningon `CONFIG_BPF_LSM` and `CONFIG_DEBUG_INFO_BTF` in `build-kernel.sh` is pending. **The image has not-been booted on a board yet.**+been booted on a board yet.** (Later: both options are on since 0.8.1's `-2+lordos` kernel, see "The+LordOS kernel".)## Results on the board (2026-10-18)@@ -848,7 +857,9 @@ Notes for the image:Still to do on the board: everything in the checklist that needs a monitor (items 1, 2, 4–8, 10, 15with screenshots, 16 HDMI audio, 17), the desktop session, and booting the built image from a-second SD card or an NVMe.+second SD card or an NVMe. (Later: a 0.8.4 image was booted from a test SD card for the 0.8.4.1+release test, `ISO.md`, and the desktop shows on HDMI since 0.8.4.1, see the status at the top; the+measurements with a monitor are still to do.)## Server portability audit (aarch64)@@ -879,7 +890,7 @@ EGL/GLES/GBM ones. What follows is the result.- **Page size (16K on the Pi 5):** there's no hardcoded 4096 in `mmap`, shm or buffers.- Dumb buffers use `CREATE_DUMB`'s `size` and `pitch`.- WASM memory reserves and protects in multiples of 64 KiB (a multiple of 16K).- - The Monitor uses `sysconf(_SC_PAGESIZE)` (`monitor/mon.c:443`).+ - The Monitor uses `sysconf(_SC_PAGESIZE)` (`monitor/mon.c`).- The dmabuf feedback does `memfd` + `mmap` of an arbitrary size, which is valid.- **Unaligned reads and endianness:**- the OpenType, MaxMind DB, xz, PNG/JPEG (stb), thbrk and IME readers read byte by byte in@@ -911,6 +922,6 @@ EGL/GLES/GBM ones. What follows is the result.| `server/src/kms.c` `read_scanout_formats` | `IN_FORMATS` with `UNIVERSAL_PLANES` untested on vc4. If it fails, it stays as before || `server/src/drmcard.h` | `GETCONNECTOR` forces an EDID read per card at startup (~50 ms). Hotplug: if HDMI is plugged in after boot, lord-sessiond has already chosen the card (vc4 anyway, because it has connectors) || `server/src/sec/sandbox.c` | seccomp: check on the board that no `.lpk` app dies from a syscall that arm64 glibc uses and x86 doesn't. Landlock: the Raspberry Pi kernel might not have it; `cmdline.txt` asks for `lsm=landlock,…`. The shared helper profile (`sandbox_apply_helper`) uses the same list and is fine on arm64, but has no `ioctl`: hardware video (V4L2 on the Pi, VA-API on the PC) inside the sandbox needs it (the sandbox agent was told) |-| `server/src/monitor/mon.c:703` | The Monitor's "model name" stays empty on ARM. The Monitor agent was told (`js_sys.c`'s `arm_cpu_name` would do) |+| `server/src/monitor/mon.c` | The Monitor's "model name" stayed empty on ARM. Fixed: `lord.monitor.info().cpuModel` now comes from `js_sys_cpu_name()`, the same one About uses (`js_monitor.c`) || `server/src/install/install.c:677` | The installer uses `grub-install --target=x86_64-efi`. On the Pi it doesn't apply (it's not live, the installer doesn't appear), but it's what would have to change for an ARM64/UEFI installer || page size | Some third-party program (not LordOS) assumes 4K: Widevine, box64, old jemalloc. If needed, `kernel=kernel8.img` in `config.txt` (4K, a bit slower) |diff --git a/docs/README.md b/docs/README.mdindex 18b5a0f..258b1ca 100644--- a/docs/README.md+++ b/docs/README.md@@ -26,6 +26,8 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| [IMAGER.md](IMAGER.md) | LordOS Imager: writing LordOS to cards and sticks, in LordOS and on other computers, and the first-run file || [INSTALL-DEBIAN.md](INSTALL-DEBIAN.md) | Installing LordOS on an existing Debian 13 with one command || [VM-SETUP.md](VM-SETUP.md) | The development VM, step by step |+| [UPDATES.md](UPDATES.md) | Updating an installed system in place from the signed APT repository, and migrations |+| [TROUBLESHOOTING.md](TROUBLESHOOTING.md) | Known problems and how to fix them (for example a modified system component) || [RELEASING.md](RELEASING.md) | How a release is made: changelog, tag, build, sign, SBOM and the GitHub release notes || [../CHANGELOG.md](../CHANGELOG.md) | What changed in each version (also the body of each GitHub release) |@@ -38,6 +40,7 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| [DISPLAYS.md](DISPLAYS.md) | Several displays and HiDPI || [GPU.md](GPU.md) | GPU composition, dmabuf and the CPU path || [DOCK.md](DOCK.md) | Dock and taskbar |+| [LAYERS.md](LAYERS.md) | The desktop's stacking order: what is drawn and clicked above what || [SPOTLIGHT.md](SPOTLIGHT.md) | Search and the advanced clipboard || [TRACKPAD.md](TRACKPAD.md) | Touchpads, gestures and touchscreens || [SESSIONS.md](SESSIONS.md) | Login screen, sessions, user switching, boot splash hand-off |@@ -49,7 +52,7 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| Document | What it covers ||---|---|| [PRIVACY.md](PRIVACY.md) | App isolation, permissions, and what is isolated today |-| [FIREWALL.md](FIREWALL.md) | Per-app firewall, restrictions and domain rules |+| [FIREWALL.md](FIREWALL.md) | Per-app firewall, restrictions, domain rules and blocklists (0.8.5) || [SIGNING.md](SIGNING.md) | Package signing, trust levels and release signing || [IMMUTABLE.md](IMMUTABLE.md) | Design study: an immutable edition with A/B system images (0.8.2, experimental prototype) || [SECURITY-REVIEW-0.8.0.md](SECURITY-REVIEW-0.8.0.md) | Security review before 0.8.0-beta: every finding and its status |@@ -72,8 +75,9 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| [DOCUMENTS.md](DOCUMENTS.md) | PDFs, archives, fonts and emoji || [PRINTING.md](PRINTING.md) | Printing and scanning || [MEDIA.md](MEDIA.md) | Photos, Player, Screenshots, Camera and Recorder |+| [VIDEO.md](VIDEO.md) | Video in the browser without hardware decoding (H.264 instead of VP9/AV1) || [MAIL.md](MAIL.md) | Mail, Calendar, Contacts and Reminders |-| [MONITOR.md](MONITOR.md) | Monitor: usage, network map, firewall, cooling |+| [MONITOR.md](MONITOR.md) | Monitor: usage, processes, network map and connections, firewall, disk health, cooling || [SYSTEM.md](SYSTEM.md) | Disks, Backups, Logs, Clock and Help |## System and hardware@@ -84,6 +88,14 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| [NETWORK.md](NETWORK.md) | Networking and VPNs || [SOUND.md](SOUND.md) | Sound (PipeWire) || [FANS.md](FANS.md) | Fan control on the Raspberry Pi 5 and PCs |+| [BENCHMARK.md](BENCHMARK.md) | System Information (0.8.5), LordBench and hardware reports: design and status |++## Measurements and validation++| Document | What it covers |+|---|---|+| [PAPER-VALIDATION.md](PAPER-VALIDATION.md) | Each claim of the paper, how it is checked and its state |+| [RESULTS.md](RESULTS.md) | Versioned results: measurements per version and machine, with the commands that produced them |## Images and assets@@ -95,6 +107,9 @@ Website: [lordos.org](https://lordos.org) · Brand kit: [LORDOS-BRAND.md](LORDOS| [iso-final/](iso-final/) | Screenshots of the final ISO test || [polish/](polish/) | Before and after screenshots of the visual polish pass || [packs/](packs/) | Sample language pack and script test text |+| [classic/](classic/) | Screenshots of the classic theme and the default theme, light and dark |+| [imager/](imager/) | Screenshots of LordOS Imager (native app and desktop app) |+| [qa/](qa/) | Screenshots of the app-by-app QA pass (see [VM-SETUP.md](VM-SETUP.md)) |## Research notesdiff --git a/docs/SPOTLIGHT.md b/docs/SPOTLIGHT.mdindex ca46aab..dc8e04b 100644--- a/docs/SPOTLIGHT.md+++ b/docs/SPOTLIGHT.md@@ -44,6 +44,7 @@ Sections are ordered by their best result; the calculator always goes on top.| Notes | `~/Notes/*/nota.md` (title from the Notes app's YAML header, and the content); the section only appears if the Notes app is present | `wm.open('notes', { args: { slug } })` || Clipboard | texts from the history | copies again || Store | `lord.pkg.search`: only AppStream apps that aren't installed, up to 5 | `wm.open('store', { args: { search } })` |+| Help | the Help articles, through `registerSpotlightSource` (`sdk/help.js`; see `SYSTEM.md`, "Help") | the article in Help |**Relevance:**- For the name: prefix > word > substring > fuzzy (the letters in order).@@ -70,7 +71,9 @@ Sections are ordered by their best result; the calculator always goes on top.| Chosen with ❖V and the 8 key: «360» was pasted into the Settings search box, which had focus | Settings → Clipboard |There is a single one for the whole session: the Terminal, LordOS's text fields and Linux apps-(the compositor acts as the bridge; see `WAYLAND.md`). The history stores everything copied in+(the compositor acts as the bridge; see `WAYLAND.md`), and since 0.8.3 X11 apps through Xwayland+(the X window manager, `wl/xwm.c`, offers LordOS's clipboard to X only while an X window has the+keyboard). The history stores everything copied inany of them: texts, links, colors, code, paths and images. For each entry it stores the originand the time.@@ -152,5 +155,6 @@ Sensitive content never enters the history, but it can still be pasted:still missing.- Formats that aren't text or PNG (HTML, `text/uri-list` with files): today they pass betweenLinux apps while the source app stays open, but they don't go into the history.-- Search: searching file contents (today, names only), contacts and mail, which don't exist- yet, and «Lock screen», which doesn't exist (M8).+- Search: searching file contents (today, names only), contacts and mail (the apps exist since+ M9, but they are not search sources yet), and a «Lock screen» action (locking exists, ❖L, but+ Search only offers dark/light mode and log out).diff --git a/docs/SYSTEM.md b/docs/SYSTEM.mdindex 10b1bd7..a7d5612 100644--- a/docs/SYSTEM.md+++ b/docs/SYSTEM.md@@ -77,6 +77,10 @@ All are in the closed table of `admin.c` (macro `DISK_ADMIN_ACTIONS` in `disk/diLong actions send `LOG progress phase=<table|mkfs|erase|write|verify> done=<n> total=<n>`, whichthe app shows as a bar.+Since 0.8.5 (in development) Files' sidebar lists every disk too and uses the same actions:+`disk-mount` when an unmounted one is clicked (an internal disk asks for an administrator, as here),+and `disk-eject` or `disk-unmount` from its ⏏ (`FILES.md`).+### Security- **The same rules for all of them, on the root side (`target()` in `disk_admin.c`):**@@ -90,7 +94,7 @@ the app shows as a bar.down to the real disks. Only `disk-smart` and the `smart-*` actions accept it: they only read,or start the disk's own self-test, which does not change data.- **Who can:**- - internal disks, only an administrator (group `sudo`);+ - internal disks, only an administrator (groups `sudo`, `admin` or `wheel`);- removable ones (USB, `removable=1`, `mmc` cards), any session user, like udisks with activesessions;- reading SMART, anyone.@@ -403,7 +407,8 @@ In the **Backups** tab: snapshots by day, the tree of each one (with real sizes)- **The same rules as `lord.fs`:** it only writes in the home folder and the user's disks(`fsops_allowed`, on the resolved folder), never in protected places (`fsops_protected`:`~/.local/share/applications`, `~/.config/autostart`, `~/.local/share/lordos/apps`,- `settings.json`, `permisos.json`, `backup.json`). A `.desktop` file planted in a backup is not+ `settings.json`, `permisos.json`, `backup.json`, and also `firewall.json`, the blocklists, the+ Mail accounts and cache and the Passwords vaults, the whole list in `server/src/fsops.c`). A `.desktop` file planted in a backup is notrestored, not even through a link in the home folder that points to a protected folder.- **No escapes through the backup:** the requested path is validated (`bk_rel_valid`) and itsresolved folder must stay inside the snapshot.@@ -710,6 +715,8 @@ dismissNotification(id);- Clicking the banner runs the first action; the × closes it.- `notifyHistory`: the last 50 of the session, in memory only.- Up to three actions per notification. The API is stable: Clock and Backups use it.+- Linux apps reach the same banners through the session's `org.freedesktop.Notifications` server+ (`server/src/hw/notifyd.c`), with per-app settings in Settings → Notifications (`SETTINGS.md`).### Screenshotsdiff --git a/docs/TERMINAL.md b/docs/TERMINAL.mdindex 132f804..f7131c4 100644--- a/docs/TERMINAL.md+++ b/docs/TERMINAL.md@@ -129,7 +129,7 @@ Status: ✅ done and tested in the VM · 🟡 partial · ⏳ pending · — does| Per-line timestamps | ✅ | ❖⇧E || Ctrl/❖+click on paths and links | 🟡 | paths under `$HOME` open Files; URLs are copied (there is no browser) || Instant Replay | ✅ | ❖⌥B, up to 1200 frames / 6 MB per session |-| Log the session to a file, save the contents | ✅ | `~/.local/share/lordos/terminal/`, `~/Documentos` |+| Log the session to a file, save the contents | ✅ | `~/.local/share/lordos/terminal/`, the documents folder (`XDG_DOCUMENTS_DIR`, in the user's language) || Broadcast input to all panes | ✅ | ❖⌥I || Alert when the command finishes | ✅ | ❖⌥A |diff --git a/docs/VIDEO.md b/docs/VIDEO.mdindex a35661a..928b4c4 100644--- a/docs/VIDEO.md+++ b/docs/VIDEO.md@@ -200,7 +200,9 @@ the automatic mode both go from 1080p to 720p). At 25 fps both play smoothly (1- Firefox: AV1 off only (VP9 stays, no notice) until the extension is signed.- Automatic trusts the system probe: if VA-API lists VP9/AV1 but the browser doesn't actually usethe hardware decoder, the video is still decoded in software; choose **Always** there.- Not tested on a machine with real hardware decoding (no GPU on the test host).+ Not tested on a machine with real hardware decoding of VP9 or AV1 (no GPU on the test host). On a+ Raspberry Pi 5 (0.8.4.1 release test, `ISO.md`) Automatic found that the board can't decode VP9 or+ AV1 in hardware and asked the sites for H.264.- H.264 on YouTube stops at 1080p; with the optimization on, higher resolutions aren't offered.- The setting is system-wide (the browsers read system files); several users share it.- A policy change counts from the next page load; Firefox needs a restart.diff --git a/docs/WINDOWS.md b/docs/WINDOWS.mdindex 9c1cdc5..20563d7 100644--- a/docs/WINDOWS.md+++ b/docs/WINDOWS.md@@ -56,7 +56,9 @@ wm.beginResize(id, edges) // edges as in xdg_toplevel.resize: 1 top, 2 botto- Limits: the minimum size is the manifest's `minSize` (Linux apps, 160×100). The frame doesn't goabove the work area (the menu bar) and 48 px always remain visible.- `xdg_toplevel.move` and `xdg_toplevel.resize` from apps that draw their own frame (GTK, Chromium- with CSD) use the same thing (`sdk/wayland.js`).+ with CSD) use the same thing (`sdk/wayland.js`). Since 0.8.3 X11 apps under Xwayland that draw+ their own frame ask with `_NET_WM_MOVERESIZE`, which the window manager for X (`wl/xwm.c`) turns+ into the same request.- If the theme didn't mark the window's node (`wm.frameRef`), or the window is maximized,`beginMove` returns `false` and the theme can fall back to its old JS dragging.