Skip to content

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.

Merge branch 'v084-csd'

Federico Pereira00c6f672f9f5
diff --cc CHANGELOG.md
index 45cb84f,bdcbf2f..7beb77f
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -10,7 -10,33 +10,33 @@@ of the matching [GitHub release](https:
## [Unreleased]
+ ## [0.8.4] - Unreleased
+
+ ### Changed
+
+ - **Browsers with a single top bar.** Chromium and Firefox now draw their own bar, with the tabs in
+ the title bar and the window buttons inside it, instead of the LordOS frame on top. In Chromium
+ the buttons are LordOS's traffic lights (from LordOS's GTK theme, sized like LordOS's own frame);
+ Firefox keeps its own button style. Both put them where the LordOS theme does: on the left in Lord
+ Default, on the right in Classic, and follow a theme or light/dark change live. Going back to the
+ LordOS frame is one switch in each browser («Use system title bar and borders» in Chromium,
+ «Title Bar» in Firefox), and it now applies right away, without reopening the window. Systems
+ upgraded from 0.8.3 get the new defaults for Firefox, and for new Chromium profiles; an existing
+ Chromium profile keeps its frame until its user switches.
+
+ ### Fixed
+
+ - **Two title bars in Chromium.** With «Use system title bar and borders» off, Chromium drew its own
+ bar and LordOS still put its frame on top: the compositor now honors the frame an app asks for
+ (xdg-decoration and the GTK 3 decoration protocol), also when it changes while the window is
+ open; the window keeps its place, size, maximized state, focus and Dock entry.
+ - **Linux app windows disappeared after switching between Lord Default and Classic** (they stayed
+ open but invisible): they now come back in the new theme, maximized ones still maximized.
+ - **The window menu of apps that draw their own bar.** A right click on a GTK app's own title bar
+ now opens the theme's window menu (Minimize, Zoom, Close; in Classic also Restore, Snap layouts
+ and the snap halves).
+
-## [0.8.3] - Unreleased
+## [0.8.3-beta] - 2026-10-19
### Added
diff --cc docs/UPDATES.md
index 809cdd5,804cb70..80fc4eb
--- a/docs/UPDATES.md
+++ b/docs/UPDATES.md
@@@ -196,7 -196,7 +196,8 @@@ Today's migrations
| `001-0.8.1-network-permissions` | Enables `lord-netperm.service` (per-app network permissions) where `lordos.service` is enabled. The ISO, the Pi image and `install.sh` already did; a system set up with `apt` alone had it off. Runs once: disabling it later sticks. |
| `002-0.8.1-root-ssh-keys` | 0.8.1 adds `PermitRootLogin no` (`/etc/ssh/sshd_config.d/10-lordos.conf`). On an **upgrade** from 0.8.0 with SSH installed and keys in `/root/.ssh/authorized_keys` (a VPS run as root), it writes `09-lordos-root-keys.conf` with `PermitRootLogin prohibit-password`, so root keeps logging in with keys (never passwords) instead of being locked out at the next restart. New installs never get it; delete the file to apply LordOS's default. |
| `003-0.8.2-drivetemp` | 0.8.2 ships `/usr/lib/modules-load.d/lordos-drivetemp.conf` (SATA disk temperatures in Monitor → Disks, read at boot). On a running system it loads `drivetemp` once, so the temperatures show without a restart. Does nothing without systemd (an image being built) or where the kernel has no `drivetemp`. |
+| `004-0.8.3-smartd-off` | 0.8.3 ships a drop-in that keeps Debian's smartd (`smartmontools.service`) off unless `/etc/lordos/smartd-enabled` exists ([SYSTEM.md](SYSTEM.md), "smartd"). A condition is only checked at start, so a smartd already running from an earlier smartmontools install is stopped once. Does nothing without systemd, without smartmontools or where an administrator opted in. |
+ | `005-0.8.4-browser-frames` | 0.8.4 makes the preinstalled browsers draw their own bar with LordOS's window buttons (`WAYLAND.md`, "The browsers by default"). Where `/etc/chromium/master_preferences` still has the 0.8.3 ISO's `"custom_chrome_frame": false` it becomes `true` and the GTK theme is added (new Chromium profiles only); where `/etc/firefox-esr/lordos.js` is still exactly the 0.8.3 file it becomes `inTitlebar` 1 (every Firefox profile whose user didn't change «Title Bar»). Anything an administrator changed is kept; home folders are not touched. |
**Settings migrations** (each user), in `sdk/settings.js`: `MIGRATIONS` is a list of
`[schema, (settings) => newSettings]` applied in order when the session loads
diff --cc docs/VM-SETUP.md
index 975d600,a594077..aea3b4d
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@@ -1318,26 -1318,32 +1318,56 @@@ package's files by `~/deploy-remotesec-
and the backup removed, `lordos.service` restarted on the package's 0.8.2 binaries, at the login
screen. Network untouched.
-## Step 37 — 0.8.4: browsers with their own bar (VM 119 `lordos-spot`, October 19)
+## Step 37 — 0.8.3 release test (VMs 116, 117, 120 and the Raspberry Pi, October 19)
+
+See `ISO.md`, "Release test (0.8.3 Beta, October 19)".
+
+- **VM 116:** the release tree in `~/LordOS-iso`, built there; ISO and `.deb` in
+ `/var/tmp/lordos-iso/out/` (the 0.8.0 and 0.8.1 ISOs there were removed to make room: identical
+ copies are in Proxmox's `local:iso`). Nothing installed.
+- **Proxmox:** `local:iso/lordos-live-0.8.3-amd64.iso` added. A temporary typing helper in the
+ host's `/root` was removed afterwards.
+- **VMs 117 and 120:** a Proxmox snapshot `r083pre` first; then 120 got a fresh 0.8.2 install from
+ the 0.8.2 ISO (test user `rtester`, `openssh-server`, a sudoers drop-in, `lordos.sources` on
+ `apt-staging`, smartmontools, xterm) and was upgraded twice (Store, then apt from a second
+ snapshot), and 117 installed the 0.8.3 ISO. Both were rolled back to `r083pre` (ISO, boot order
+ and disks as before: the earlier "Test User" installs, at the login screen) and the snapshots
+ deleted.
+- **Raspberry Pi 5 (172.17.0.24):** built the arm64 package and the image in
+ `/var/tmp/lordos-src-083` and `/var/tmp/lordos-rpi-v083b`. The installed LordOS went from 0.8.0
+ to 0.8.3 with apt: `/usr/share/keyrings/lordos-archive-keyring.gpg` and
+ `/etc/apt/sources.list.d/lordos.sources` (the live repository) added, `lordos` 0.8.3 with
+ `xwayland` and its 14 dependencies installed, migrations 001–004 applied (002 wrote
+ `/etc/ssh/sshd_config.d/09-lordos-root-keys.conf`, so root keeps logging in with keys only), and
+ `lordos.service` restarted (only the login screen was running). No reboot; network, the
+ `lordbasex` account and the SD partitions untouched.
++
++## Step 38 — 0.8.4: browsers with their own bar (VM 119 `lordos-spot`, October 19)
+
+ See `WAYLAND.md` ("Who draws the frame", "The browsers by default"). On VM 119 (172.17.0.54), tree
+ in `~/LordOS-csd`, built there (`make -C server`, `make -C server build/deco-client`,
+ `make -C server test`) and installed over `/usr/lib/lordos` by `~/deploy-csd-119.sh` (it saved
+ `/usr/lib/lordos`, the original `/etc/chromium/master_preferences` and `settings.json` first, in
+ `/var/backups/lordos-csd-bak`).
+
+ - **Installed for the tests:** `gsettings-desktop-schemas` (the ISO has it; without it GTK 3 can't
+ read the theme and the button layout from the keyfile backend, and Chromium's GTK theme shows
+ Adwaita's buttons on the right), removed at the end. `assets/gtk/LordOS*` copied to
+ `/usr/share/themes/` (the package does that), removed at the end.
+ - **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the
+ end), English, light, Lord Default in `settings.json` (restored at the end).
+ - **Browsers:** throwaway profiles in `/tmp` (`chromium --user-data-dir=/tmp/csd-chr2`,
+ `firefox-esr --profile /tmp/csd-ff --no-remote`), started from SSH with the session's environment
+ (`WAYLAND_DISPLAY=wayland-0`, `XDG_SESSION_TYPE=wayland`, `GSETTINGS_BACKEND=keyfile`, the session
+ bus). The user's own browser profiles were not touched. `master_preferences` was edited to test the
+ new initial preferences on a new profile and put back.
+ - **Input and screenshots:** `lord-qmp-input.py 119 1280 800` and `lord-type.py 119` from the host,
+ `screendump` holding `flock /tmp/sistema-119-screen.lock`. The "before" screenshot ran the saved
+ October 18 install for a few minutes, then the new build again.
+ - **The migration** (`005-0.8.4-browser-frames.sh`) ran against copies under a scratch root
+ (`LORDOS_MIGRATION_ROOT`): the 0.8.3 files change, a second run changes nothing, files an
+ administrator edited stay.
+ - **Undone at the end:** `/usr/lib/lordos` restored from the backup (`diff -r` empty),
+ `master_preferences` and `settings.json` restored, the themes, the schemas package, `session.conf`,
+ the profiles, the tree, the script and the backup removed, `lordos.service` restarted to the login
+ screen. No network or Proxmox setting was touched.
diff --cc docs/WAYLAND.md
index acbec97,056646d..0382d02
--- a/docs/WAYLAND.md
+++ b/docs/WAYLAND.md
@@@ -209,7 -275,8 +275,8 @@@ What a window with its own bar still ge
they change.
Tested in VM 118 with Chromium 155, Firefox ESR 153, Mousepad (GTK 3) and GNOME Calculator
- (GTK 4, libadwaita).
-(GTK 4, libadwaita); the 0.8.4 frame changes on VM 119 (`VM-SETUP.md`, step 37) with Chromium 155,
++(GTK 4, libadwaita); the 0.8.4 frame changes on VM 119 (`VM-SETUP.md`, step 38) with Chromium 155,
+ Firefox ESR 153, GTK Demo (GTK 4) and foot, both themes, light and dark.
## X11 apps (Xwayland)