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 v083-classic (0.8.3)
Federico Pereira078746fd203c
diff --cc CHANGELOG.mdindex e9e232a,8e87bae..9edb12e--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -14,33 -14,42 +14,67 @@@ of the matching [GitHub release](https:### Added+- **X11 apps.** Programs that only speak X11 (xterm, Java/Swing apps, many games and older tools)+ now open in LordOS through Xwayland (the `xwayland` package), with the theme's window frame, their+ icon in the Dock (matched to their launcher by `WM_CLASS`), menus and tooltips above everything,+ fullscreen, minimize and close, and LordOS's cursor. Xwayland only starts when an X11 app+ connects and stops 10 seconds after the last one closes. LordOS's own X window manager is+ written in C and speaks the X11 protocol itself, without new libraries in `lord-server`.+- **Clipboard with X11 apps**, both ways, for the normal clipboard and the primary selection+ (select to copy, middle click to paste); large copies and images included.+- **Primary selection for Wayland apps** (middle-click paste between GTK, Qt and other apps).+ - **Classic, a second full appearance.** The Classic theme is no longer a template: it is a+ complete desktop for people used to a taskbar layout, with the same apps as Lord Default. A+ centered taskbar (or aligned to the start, on any side of the screen) with the start button,+ search, task view, the pinned and open apps and the Trash last; a start menu with a search field+ that searches like the system search (apps, settings, files, notes, the calculator, Help), a grid+ of pinned apps you arrange with a right click, recently used apps, every app A–Z, and the user+ and power button (Lock, Switch User, Log Out, Restart…, Shut Down…); a tray with quick settings+ (network, Bluetooth, Do Not Disturb, Night Light, dark mode, transparency, volume, what is+ playing, battery) and a notification panel with a month calendar; notifications above the+ taskbar; and a window frame with the title at the start and the buttons at the end. Everything+ is our own design: LordOS icons drawn by the theme, Inter, the LordOS wallpapers and names.+ Switch between the two in **Settings → Appearance → Desktop style**, live and without logging+ out: the windows that were open come back in the new one. Light and dark mode, right-to-left+ languages and the accent colors work in both. See [docs/DESIGN.md](docs/DESIGN.md), "Classic".+ - **Window snapping.** In Classic, drag a window to the left or right edge to fill that half of the+ screen, to a corner for a quarter, or to the top edge to maximize it; a preview shows where it+ will go. Hovering over the maximize button offers layouts (halves, two thirds and one third,+ thirds, quarters), and Super+arrows move the window in front between them. Dragging a snapped+ window away gives it back its size. See [docs/WINDOWS.md](docs/WINDOWS.md), "Snapping".+ - **Task view.** Super+Tab (or the taskbar button) shows every window side by side, live and+ smaller, over a dimmed desktop: click one to bring it to the front, or close it from there.+ - **Themes restyle every app.** The shared controls (buttons, fields, segmented controls, sidebars,+ menus, tooltips, grouped forms, confirmations and the Restart/Shut Down sheet) now take their+ shape from the theme: corner radii, a light or accent menu highlight, an accent bar or a fill for+ the selected sidebar row, an underline or a ring on the focused field, and bordered buttons. Lord+ Default looks as before; Classic uses smaller radii, borders and subtle highlights. Isolated+ apps (Mail, Calendar, Contacts, Reminders, Passwords) follow it too.++ ### Changed++ - Settings → Desktop & Dock in Classic adds **Taskbar alignment** (center or start).+ - The theme engine paints a scaled window that contains a blurred surface (a translucent+ Terminal) at its scaled size; its blur then only shows the window's own content. Before, such a+ window was drawn at full size during the Dock's minimize effect.-## [0.8.2] - Unreleased+### Security++- X11 apps run in their app's scope, so per-app firewall rules and the Monitor apply to them.+- X11 apps never see Wayland apps, LordOS's screen, Passwords or the keyring prompt, nor the keys+ typed into them; what is copied outside X enters X only while an X window has the keyboard, and+ passwords copied in Passwords never do. Synthetic input between X11 apps (XTEST) is off.+ Xwayland runs without network, in its own scope. X11 apps can still see each other, as in any X11+ desktop (see the privacy documentation).+- Apps with device or "no files" restrictions get no X display.+- Clipboard offers to Wayland apps are bound to the selection they were made for and to the app+ with the keyboard.++### Fixed++- Java (AWT/Swing) windows were blank or shifted (non-reparenting window manager).++## [0.8.2-beta] - 2026-10-19### Addeddiff --cc docs/ROADMAP.mdindex c122ab7,422dac2..0ae6427--- a/docs/ROADMAP.md+++ b/docs/ROADMAP.md@@@ -538,24 -516,20 +538,24 @@@ Details in `MAIL.md`. Tested on VM 123`tryboot` (phase 3), Debian packages as system extensions and delta updates (phase 4), `/etc` andexecution hardening (phase 5). The classic edition stays as it is.-- [ ] **Xwayland** (X11 app compatibility). Today LordOS runs Wayland apps only, so programs that- speak only X11 don't start. Plan:- - start `Xwayland` on demand (rootless) when an X11 client connects, with its own `DISPLAY`- socket; the compositor (`server/src/wl/`) acts as the X window manager (XWM: map, stack,- focus, move and resize, titles and icons, transient/popup windows, our window frame);- - clipboard and drag and drop bridged between X11 and Wayland;- - HiDPI and fractional scaling for X11 windows, multi-monitor positions;- - the same per-app identity as Wayland apps (cgroup scope, firewall, Dock grouping), so X11 apps- get the per-app network and device restrictions too;- - security: X11 apps can read each other's input and windows by design; X11 clients are isolated- from Wayland apps and protected windows (Passwords) are never exposed to them; documented in+- [x] **Xwayland** (X11 app compatibility) — 0.8.3, see `WAYLAND.md` ("X11 apps (Xwayland)") and+ `PRIVACY.md` ("X11 apps"):+ - [x] `Xwayland` on demand (rootless), started by the first connection to the session's X socket+ and stopped 10 s after the last X app; our own X window manager in C (map, stacking, focus,+ move and resize, titles, `WM_CLASS` → `.desktop`, override-redirect menus and tooltips,+ fullscreen, minimize, close, our window frame and cursor);+ - [x] clipboard and primary selection bridged both ways (and `zwp_primary_selection_v1` for+ Wayland apps); drag and drop X11 ↔ Wayland: not yet (LordOS has no Wayland drag and drop yet);+ - [x] HiDPI policy (scale 1, scaled by the compositor) and positions across displays; not tested on+ a HiDPI display;+ - [x] the same per-app identity as Wayland apps (scope, firewall, Dock grouping); restricted apps+ get no X display;+ - [x] X11 apps never see Wayland apps, protected windows or keys typed into them; documented in`PRIVACY.md`;- - tests with real X11 apps (an xterm-style terminal, a Java/Swing app, a game) and screenshots.+ - [x] tests with real X11 apps (XTerm, xeyes, a Swing app, Neverball), CPU and GPU paths.+ - [ ] later: a separate or "untrusted" X display for restricted apps; X11 ↔ Wayland drag and drop;+ sharp X11 apps on HiDPI displays.- - [ ] **Turn the "Classic" theme into a second full appearance** (Settings → Themes), for people coming from the+ - [x] **Turn the "Classic" theme into a second full appearance** (0.8.3; Settings → Appearance → Desktop style, see `DESIGN.md`, "Classic"), for people coming from themost common desktop layout: a centered taskbar with a start menu, pinned and running apps, asystem tray with quick settings and a notification panel, snap layouts for windows, roundedcorners and translucent materials. Today `themes/classic` is only a template (taskbar and startdiff --cc docs/VM-SETUP.mdindex 83b7831,92f6b1a..5a3113a--- a/docs/VM-SETUP.md+++ b/docs/VM-SETUP.md@@@ -1247,26 -1247,28 +1247,51 @@@ removed, so `diff -r` against the backutests) restored from the backup, the Mail restriction in `firewall.json` removed, and the testdata deleted (`~/.config/lordos/mail`, `~/.local/share/lordos/mail`, the four apps'`appdata` folders, two files in `~/Documents`). Nothing in the network configuration was touched.-## Step 34 — The Classic theme as a second full appearance (VM 119 `lordos-spot`, October 19)++## Step 34 — 0.8.3: X11 apps with Xwayland (VM 118 `lordos-notes`, October 19)++See `WAYLAND.md` ("X11 apps (Xwayland)") and `PRIVACY.md` ("X11 apps"). Installed with+`--no-install-recommends`:++| Package | What for |+|---|---|+| `xwayland` 2:24.1.6 | X11 apps (the only one LordOS needs; it brings `xserver-common`, `x11-xkb-utils`) |+| `xterm`, `x11-apps` (xeyes, xwd), `x11-utils` (xprop, xwininfo, xev) | test apps and X inspection |+| `xclip`, `xinput`, `xdotool` | clipboard tests, the keyboard-snoop test (`tests/xwayland/keysnoop.sh`) and reading the X pointer (XTEST is off, so `xdotool` can't type) |+| `openjdk-21-jdk-headless`, `openjdk-21-jre` | the Swing test app (`~/xwl-tests/SwingTest.java`, a `.desktop` with `StartupWMClass=SwingTest`, removed after the tests) |+| `neverball` | an SDL game (`SDL_VIDEODRIVER=x11`) |++- Build: `make -C server` (no new build dependency: the primary-selection XML is in+ `wayland-protocols`), plus `make -C server build/clip-offers` for `tests/xwayland/selections.sh`.+- The GPU path was tested with a temporary `lordos.service.d` drop-in `Environment=LORD_GPU=1`+ (llvmpipe), removed afterwards.+- Input: a uinput tablet+keyboard (`~/uinput-xwl-118.py`, the same as the earlier steps' scripts)+ mapped to the whole desktop (2987×1067 on this VM's two displays).+- The installed LordOS was backed up to `~/xwayland-backup-20261019` and restored after the tests;+ `firewall.json` was restored too.+++## Step 35 — The Classic theme as a second full appearance (VM 119 `lordos-spot`, October 19)++ See `DESIGN.md` ("Classic") and `WINDOWS.md` ("Snapping"). On VM 119 (172.17.0.54), tree in+ `~/LordOS-classic`, built there (`make -C server`, `make -C server test`) and installed into+ `/usr/lib/lordos` (`lord-server`, `lord-media`, `lord-vault`, `lord-maild`, the theme bundles, the+ app host, the system apps, `assets/{fonts,locales,shell,icons,mascot,monitor,help}` and the wallpaper+ JPEGs under `assets/wallpapers`, which this older install didn't have) by `~/deploy-classic-119.sh`.+ The installed tree was saved first in `/var/backups/lordos-classic-bak` and put back at the end.++ - **Nothing installed with apt.** No Proxmox or network setting was touched (`eth0` keeps 172.17.0.54).+ - **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the+ end). A fresh session needs the old one's `lord-server` ended first, then `/run/lordos/autologin-done`+ removed and `systemctl restart lordos` (restarting the service alone keeps the open session).+ - **Screenshots and measurements:** a scratch-only harness (never in the repo) was built in front of+ both themes' bundles: it read `~/.cache/lordos-shot.json` and opened one app at a centered frame,+ switched theme, mode or language. Screenshots with `screendump` from the Proxmox host, the pointer+ with `lord-qmp-input.py 119 1280 800`, keys with `qm monitor 119` `sendkey`, holding+ `flock /tmp/sistema-119-screen.lock`. Window drags for the frame times with a QMP script in the+ host's `/tmp` (deleted afterwards); lord-server's own `drag:` lines in `~/.cache/lordos/session.log`.+ - **Test notifications** with `notify-send` (they live in the session's memory only).+ - **Undone at the end:** `/usr/lib/lordos` put back from the backup (the files the deploy added+ removed, the rest copied back; `diff -r` against the backup empty, then the backup deleted),+ `~/.config/lordos/settings.json` restored from its copy, `~/.cache/lordos-shot*.json`,+ `~/shot-harness`, `~/deploy-classic-119.sh` and `~/LordOS-classic` deleted. The VM ends at the+ login screen.