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.

Release 0.8.3-beta

Federico Pereira36cf07b44c63
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index a30d0b9..da02ff7 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -11,8 +11,8 @@ body:
id: version
attributes:
label: LordOS version
- description: Open the About LordOS app and copy the version (for example "0.8.2 · Beta").
- placeholder: 0.8.2 · Beta
+ description: Open the About LordOS app and copy the version (for example "0.8.3 · Beta").
+ placeholder: 0.8.3 · Beta
validations:
required: true
- type: dropdown
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f296ffe..dcf2fd7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,7 +10,7 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
## [Unreleased]
-## [0.8.3] - Unreleased
+## [0.8.3-beta] - 2026-10-19
### Added
@@ -63,6 +63,8 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
### Changed
- Settings → Desktop & Dock in Classic adds **Taskbar alignment** (center or start).
+- The `lordos` package recommends `xwayland`, and the ISO and the Raspberry Pi 5 image include it,
+ so X11 apps open out of the box.
- 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.
@@ -127,6 +129,7 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
### Fixed
- Java (AWT/Swing) windows were blank or shifted (non-reparenting window manager).
+- The Passwords and Backups icons sat off center in the Dock and the launcher.
- **Blocking an app now cuts the connections it already has open.** Turning an app's rule off in
Monitor → Network (or adding a deny rule for a destination or domain, or a restriction such as
"no internet") counted its new connections as denied, but what was already open kept flowing:
@@ -138,6 +141,33 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
connection as denied and shows the dropped bytes as "Blocked traffic" in the app's details. See
[docs/FIREWALL.md](docs/FIREWALL.md), "Existing connections are cut".
+### Known issues and limitations
+
+- **X11 apps need Debian's `xwayland` package.** New installs from the ISO and the Raspberry Pi 5
+ image, `install.sh` and `apt upgrade` bring it (the `lordos` package now recommends it). The
+ Store's update installs only what the package depends on, so after updating from the Store,
+ install **xwayland** from the Store (or `sudo apt install xwayland`) to open X11 apps; Wayland
+ apps don't need it.
+- X11 apps can see each other, as on any X11 desktop; a separate display for restricted X11 apps,
+ drag and drop between X11 and Wayland apps and sharp X11 apps on HiDPI displays come later.
+- The other known issues of 0.8.2 still apply.
+
+### Upgrading
+
+- **From 0.8.2 or 0.8.1:** Store → Updates shows "LordOS 0.8.3 is available" with these notes;
+ **Update** installs it, and a restart finishes it. `sudo apt update && sudo apt upgrade` does the
+ same. The update runs migration 004 once (it stops Debian's smartd if smartmontools left it
+ running; from 0.8.1, migration 003 runs first); `ls /var/lib/lordos/migrations` lists the ones
+ applied. Your settings are kept.
+- **Remote desktop after the update:** connections from public internet addresses are refused
+ unless you choose **Any address** (or add them to the allowlist) in Settings → Sharing; the local
+ network and a VPN of this computer keep working. Browsers that were signed in before sign in
+ once more.
+- **From 0.8.0 (once):** run `curl -fsSL https://lordos.org/install.sh | sh` (a system installed
+ from the 0.8.0 ISO has no `curl`: run `sudo apt update && sudo apt install -y curl` first). It
+ upgrades in place to 0.8.3, runs migrations 001 to 004 and adds the LordOS repository; from then
+ on new versions come through Store → Updates.
+
## [0.8.2-beta] - 2026-10-19
### Added
@@ -1041,7 +1071,8 @@ we published. See [docs/SIGNING.md](docs/SIGNING.md).
Never published; superseded by 0.8.0-beta.
-[Unreleased]: https://github.com/lordbasex/LordOS/compare/v0.8.2-beta...HEAD
+[Unreleased]: https://github.com/lordbasex/LordOS/compare/v0.8.3-beta...HEAD
+[0.8.3-beta]: https://github.com/lordbasex/LordOS/compare/v0.8.2-beta...v0.8.3-beta
[0.8.2-beta]: https://github.com/lordbasex/LordOS/compare/v0.8.1-beta...v0.8.2-beta
[0.8.1-beta]: https://github.com/lordbasex/LordOS/compare/v0.8.0-beta...v0.8.1-beta
[0.8.0-beta]: https://github.com/lordbasex/LordOS/releases/tag/v0.8.0-beta
diff --git a/docs/UPDATES.md b/docs/UPDATES.md
index d860737..809cdd5 100644
--- a/docs/UPDATES.md
+++ b/docs/UPDATES.md
@@ -196,6 +196,7 @@ 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. |
**Settings migrations** (each user), in `sdk/settings.js`: `MIGRATIONS` is a list of
`[schema, (settings) => newSettings]` applied in order when the session loads
diff --git a/package-lock.json b/package-lock.json
index 20d94cb..9aca2f2 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "lordos",
- "version": "0.8.2",
+ "version": "0.8.3",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "lordos",
- "version": "0.8.2",
+ "version": "0.8.3",
"dependencies": {
"react": "19.3.1",
"react-reconciler": "0.34.0"
diff --git a/package.json b/package.json
index 483be80..5fb1f4c 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
{
"name": "lordos",
"private": true,
- "version": "0.8.2",
+ "version": "0.8.3",
"description": "LordOS — React themes and apps for lord-server",
"lordos": {
"channel": "beta"
diff --git a/runtime/index.js b/runtime/index.js
index b11594f..943e87a 100644
--- a/runtime/index.js
+++ b/runtime/index.js
@@ -90,7 +90,7 @@ let updatePriority = NoEventPriority;
// react-reconciler 0.34 host interface (React 19), mutation mode like React Native.
const host = {
rendererPackageName: '@lordos/runtime',
- rendererVersion: '0.8.2',
+ rendererVersion: '0.8.3',
supportsMutation: true,
supportsPersistence: false,
supportsHydration: false,
diff --git a/sdk/system.js b/sdk/system.js
index 8e9231d..313a646 100644
--- a/sdk/system.js
+++ b/sdk/system.js
@@ -5,7 +5,7 @@ import { formatNumber, t } from './i18n.js';
export const systemInfo = () => lord.system.info();
// LordOS's own version, from the build (package.json "version" and "lordos": {"channel"}, see
-// server/Makefile): { version: '0.8.2', channel: 'Beta' (empty for a stable release), build }.
+// server/Makefile): { version: '0.8.3', channel: 'Beta' (empty for a stable release), build }.
export function lordosVersion(info) {
const i = info || systemInfo();
const id = String(i.channel || '');
diff --git a/tools/iso/build.sh b/tools/iso/build.sh
index 3b961fc..e7cb09f 100755
--- a/tools/iso/build.sh
+++ b/tools/iso/build.sh
@@ -28,7 +28,7 @@ for t in debootstrap mksquashfs xorriso grub-mkrescue mformat dpkg-deb; do
command -v "$t" >/dev/null || { echo "build.sh: missing $t (see docs/ISO.md, build packages)" >&2; exit 1; }
done
-# Live system packages. LordOS does not use X11, GNOME or KDE: only what is below.
+# Live system packages. LordOS does not use GNOME or KDE: only what is below (xwayland only for X11 apps).
PKGS_BASE="linux-image-amd64 initramfs-tools live-boot live-boot-initramfs-tools systemd-sysv udev kmod dbus dbus-user-session sudo locales tzdata
iproute2 iputils-ping less nano ca-certificates apt dpkg passwd procps"
# gsettings-desktop-schemas: without it GTK 3 apps can't read gtk-theme from the keyfile backend
@@ -39,7 +39,7 @@ PKGS_LORDOS="libwayland-server0 libwayland-client0 libxkbcommon0 xkb-data pipewi
libpoppler-glib8t64 libarchive13t64 poppler-data cups avahi-daemon exfatprogs ntfs-3g
libavcodec61 libavformat61 libavutil59 libswscale8 libswresample5 libva2 libva-drm2 mesa-va-drivers
bluez libspa-0.2-bluetooth power-profiles-daemon systemd-timesyncd shared-mime-info
- gsettings-desktop-schemas"
+ gsettings-desktop-schemas xwayland"
PKGS_FIRMWARE="firmware-amd-graphics firmware-misc-nonfree firmware-iwlwifi firmware-realtek firmware-atheros
firmware-sof-signed"
PKGS_GPU="libgl1-mesa-dri libegl1 libgles2 libgbm1 mesa-vulkan-drivers mesa-utils vulkan-tools glmark2-es2-wayland"
diff --git a/tools/iso/mkdeb.sh b/tools/iso/mkdeb.sh
index c21f297..86aea56 100755
--- a/tools/iso/mkdeb.sh
+++ b/tools/iso/mkdeb.sh
@@ -237,7 +237,7 @@ Architecture: ${DEB_ARCH:-$(dpkg --print-architecture)}
Maintainer: LordOS <[email protected]>
Installed-Size: $SIZE
Depends: libc6 (>= 2.38), libwayland-server0 (>= 1.22), libwayland-client0 (>= 1.22), libxkbcommon0 (>= 1.5), libcrypt1, libssl3t64 | libssl3, ca-certificates, passwd, procps, xkb-data$GPUDEPS$DOCDEPS$MEDIADEPS
-Recommends: pipewire-pulse, wireplumber, wpasupplicant, openvpn, fonts-noto-core, locales, tzdata, sudo, cups, cups-client, avahi-daemon, mesa-va-drivers, bluez, libspa-0.2-bluetooth, power-profiles-daemon, systemd-timesyncd, shared-mime-info, gsettings-desktop-schemas
+Recommends: pipewire-pulse, wireplumber, wpasupplicant, openvpn, fonts-noto-core, locales, tzdata, sudo, cups, cups-client, avahi-daemon, mesa-va-drivers, bluez, libspa-0.2-bluetooth, power-profiles-daemon, systemd-timesyncd, shared-mime-info, gsettings-desktop-schemas, xwayland
Section: x11
Priority: optional
Protected: yes
diff --git a/tools/rpi/build-img.sh b/tools/rpi/build-img.sh
index bd2b47e..207c11c 100755
--- a/tools/rpi/build-img.sh
+++ b/tools/rpi/build-img.sh
@@ -67,7 +67,7 @@ PKGS_BASE="initramfs-tools systemd-sysv udev kmod dbus dbus-user-session sudo lo
iproute2 iputils-ping less nano ca-certificates apt dpkg passwd procps e2fsprogs fdisk dosfstools util-linux"
PKGS_LORDOS="libwayland-server0 libxkbcommon0 xkb-data pipewire pipewire-pulse pipewire-alsa wireplumber rtkit
alsa-ucm-conf wpasupplicant openvpn fonts-noto-core fonts-noto-cjk fonts-noto-color-emoji libthai-data
- skkdic rime-data-pinyin-simp fonts-dejavu-core"
+ skkdic rime-data-pinyin-simp fonts-dejavu-core xwayland"
# Raspberry Pi: boot firmware (start*.elf are not used on the Pi 5: its firmware lives in the
# EEPROM) and Wi-Fi (CYW43455, firmware-brcm80211); kernels below
PKGS_RPI="raspi-firmware firmware-brcm80211 rsync"
diff --git a/web/content/faq/faq.json b/web/content/faq/faq.json
index f5ea755..e85d4e3 100644
--- a/web/content/faq/faq.json
+++ b/web/content/faq/faq.json
@@ -42,9 +42,9 @@
"pt": "É baseada no Debian?"
},
"a": {
- "en": "Yes, on Debian 13. The kernel, drivers, Mesa, PipeWire, CUPS, BlueZ and every package in the Store come from Debian's own mirrors and keep Debian's security updates. LordOS replaces only the graphical layer: there is no X11, GNOME or KDE underneath.",
- "es": "Sí, en Debian 13. El kernel, los drivers, Mesa, PipeWire, CUPS, BlueZ y todos los paquetes de la Tienda vienen de los mirrors de Debian y reciben sus actualizaciones de seguridad. LordOS reemplaza solo la capa gráfica: abajo no hay X11, GNOME ni KDE.",
- "pt": "Sim, no Debian 13. O kernel, os drivers, o Mesa, o PipeWire, o CUPS, o BlueZ e todos os pacotes da Loja vêm dos espelhos do Debian e recebem as atualizações de segurança dele. O LordOS substitui só a camada gráfica: por baixo não há X11, GNOME nem KDE."
+ "en": "Yes, on Debian 13. The kernel, drivers, Mesa, PipeWire, CUPS, BlueZ and every package in the Store come from Debian's own mirrors and keep Debian's security updates. LordOS replaces only the graphical layer: there is no GNOME or KDE underneath, and X11 apps run through Xwayland only when one opens.",
+ "es": "Sí, en Debian 13. El kernel, los drivers, Mesa, PipeWire, CUPS, BlueZ y todos los paquetes de la Tienda vienen de los mirrors de Debian y reciben sus actualizaciones de seguridad. LordOS reemplaza solo la capa gráfica: abajo no hay GNOME ni KDE, y las apps X11 usan Xwayland solo cuando se abre una.",
+ "pt": "Sim, no Debian 13. O kernel, os drivers, o Mesa, o PipeWire, o CUPS, o BlueZ e todos os pacotes da Loja vêm dos espelhos do Debian e recebem as atualizações de segurança dele. O LordOS substitui só a camada gráfica: por baixo não há GNOME nem KDE, e os apps X11 usam o Xwayland só quando um deles abre."
}
},
{
@@ -371,9 +371,9 @@
"pt": "Posso rodar apps Linux comuns?"
},
"a": {
- "en": "Yes, apps that speak Wayland: GTK 3 and 4 (GNOME), Qt (KDE), Firefox, Chromium and Electron apps open as normal LordOS windows, with the LordOS frame and theme. Apps that only support X11 don't run yet, because Xwayland isn't available yet.",
- "es": "Sí, las que hablan Wayland: las apps GTK 3 y 4 (GNOME), Qt (KDE), Firefox, Chromium y Electron se abren como ventanas normales de LordOS, con su marco y su tema. Las apps que solo soportan X11 todavía no funcionan, porque Xwayland todavía no está disponible.",
- "pt": "Sim, os que falam Wayland: apps GTK 3 e 4 (GNOME), Qt (KDE), Firefox, Chromium e Electron abrem como janelas normais do LordOS, com a moldura e o tema dele. Apps que só suportam X11 ainda não rodam, porque o Xwayland ainda não está disponível."
+ "en": "Yes, apps that speak Wayland: GTK 3 and 4 (GNOME), Qt (KDE), Firefox, Chromium and Electron apps open as normal LordOS windows, with the LordOS frame and theme. Apps that only support X11 open too, through Xwayland (since 0.8.3), with the same frame, Dock icon and per-app firewall.",
+ "es": "Sí, las que hablan Wayland: las apps GTK 3 y 4 (GNOME), Qt (KDE), Firefox, Chromium y Electron se abren como ventanas normales de LordOS, con su marco y su tema. Las apps que solo soportan X11 también se abren, con Xwayland (desde la 0.8.3), con el mismo marco, ícono en el Dock y firewall por app.",
+ "pt": "Sim, os que falam Wayland: apps GTK 3 e 4 (GNOME), Qt (KDE), Firefox, Chromium e Electron abrem como janelas normais do LordOS, com a moldura e o tema dele. Apps que só suportam X11 também abrem, pelo Xwayland (desde o 0.8.3), com a mesma moldura, ícone no Dock e firewall por app."
}
},
{
@@ -397,9 +397,9 @@
"pt": "Posso jogar?"
},
"a": {
- "en": "Wayland games can run with GPU acceleration: LordOS supports fullscreen, relative pointer and pointer locking, which games need, and Neverball has been tested. Games that only use X11 need Xwayland, which isn't available yet, so many games and launchers won't start for now.",
- "es": "Los juegos para Wayland pueden andar con aceleración por GPU: LordOS soporta pantalla completa, puntero relativo y bloqueo del puntero, que los juegos necesitan, y se probó Neverball. Los juegos que solo usan X11 necesitan Xwayland, que todavía no está disponible, así que por ahora muchos juegos y lanzadores no arrancan.",
- "pt": "Jogos para Wayland podem rodar com aceleração por GPU: o LordOS suporta tela cheia, ponteiro relativo e travamento do ponteiro, que os jogos precisam, e o Neverball foi testado. Jogos que só usam X11 precisam do Xwayland, que ainda não está disponível, então por enquanto muitos jogos e launchers não abrem."
+ "en": "Wayland games can run with GPU acceleration: LordOS supports fullscreen, relative pointer and pointer locking, which games need, and Neverball has been tested. Games that only use X11 run through Xwayland since 0.8.3 (Neverball was tested that way too, with OpenGL and fullscreen).",
+ "es": "Los juegos para Wayland pueden andar con aceleración por GPU: LordOS soporta pantalla completa, puntero relativo y bloqueo del puntero, que los juegos necesitan, y se probó Neverball. Los juegos que solo usan X11 andan con Xwayland desde la 0.8.3 (Neverball también se probó así, con OpenGL y pantalla completa).",
+ "pt": "Jogos para Wayland podem rodar com aceleração por GPU: o LordOS suporta tela cheia, ponteiro relativo e travamento do ponteiro, que os jogos precisam, e o Neverball foi testado. Jogos que só usam X11 rodam pelo Xwayland desde o 0.8.3 (o Neverball também foi testado assim, com OpenGL e tela cheia)."
}
},
{
diff --git a/web/content/features/linux-apps.en.md b/web/content/features/linux-apps.en.md
index 9d878b8..b2a2cc1 100644
--- a/web/content/features/linux-apps.en.md
+++ b/web/content/features/linux-apps.en.md
@@ -53,9 +53,9 @@ Deliberately absent: any protocol that lets an app capture the screen or other a
**Are Linux apps sandboxed?** Not by default. This is important: they run as your user, as on any Debian system, and can read your home folder. What LordOS adds is a per-app cgroup, attribution in the Monitor, the kernel-enforced per-app firewall (allow, deny, LAN only, no incoming connections, rules by domain or address), and restrictions you can set per app: no camera, no USB and no Bluetooth sockets (in the kernel), no microphone (LordOS's PipeWire guard plus the sound card's capture nodes), no notifications, and "no access to your files", applied from the next launch. They don't cover the clipboard, Bluetooth through BlueZ on the system bus, or programs started outside the app launcher. Only LordOS's own `.lpk` apps get the full sandbox.
-**Can a Linux app see other windows or record the screen?** Not through LordOS. The compositor only gives an app its own surfaces and offers no screen-capture protocol, there is no X server and no screen-cast portal, and a restricted app is also denied the framebuffer device, so protected windows like Passwords stay private from them too.
+**Can a Linux app see other windows or record the screen?** Not through LordOS. The compositor only gives an app its own surfaces and offers no screen-capture protocol, X11 apps only see other X11 apps (never Wayland apps or LordOS itself), there is no screen-cast portal, and a restricted app is also denied the framebuffer device, so protected windows like Passwords stay private from them too.
-**What about X11-only apps?** They don't run yet: Xwayland is not part of LordOS 0.8.2 Beta. It is planned before 1.0, with X11 apps getting the same per-app identity, firewall and restrictions. Current GTK and Qt apps speak Wayland, and so did the SDL game tested.
+**What about X11-only apps?** Since LordOS 0.8.3 Beta they open through Xwayland, started only when one of them connects, with the theme's window frame, their icon in the Dock and the shared clipboard. They get the same per-app identity, firewall and Monitor attribution as Wayland apps; apps with device or file restrictions get no X display. XTerm, a Java Swing app and an SDL game were tested.
**And Flatpak?** LordOS doesn't use or integrate it, and it hasn't been tested.
@@ -63,8 +63,8 @@ Deliberately absent: any protocol that lets an app capture the screen or other a
## Honest limits
-- **No Xwayland yet** (planned before 1.0), so no X11-only apps.
-- **Not yet:** drag and drop between apps, the middle-click primary selection, LordOS input methods (Korean, Japanese, Chinese) inside Linux apps, and app activation requests.
+- **X11 apps can see each other,** as on any X11 desktop; they are sharp only at 100 % scale.
+- **Not yet:** drag and drop between apps, LordOS input methods (Korean, Japanese, Chinese) inside Linux apps, and app activation requests.
- **SVG-only icons:** LordOS doesn't draw SVG yet. It uses the PNG icons Debian publishes for most apps, or the initial.
- **Terminal apps** with a `.desktop` file aren't shown in the app launcher; start them from the Terminal.
- **GTK 3 apps keep their own blue accent;** Qt 6's reading of the colour scheme from the portal hasn't been tested.
diff --git a/web/content/features/linux-apps.es.md b/web/content/features/linux-apps.es.md
index 6dc18cf..c24224a 100644
--- a/web/content/features/linux-apps.es.md
+++ b/web/content/features/linux-apps.es.md
@@ -53,9 +53,9 @@ Ausente a propósito: cualquier protocolo que le permita a una app capturar la p
**¿Las apps de Linux están en una caja de arena?** No de forma predeterminada. Esto es importante: corren como tu usuario, como en cualquier sistema Debian, y pueden leer tu carpeta personal. Lo que LordOS suma es un cgroup por app, la atribución en el Monitor, el firewall por app que aplica el kernel (permitir, denegar, solo LAN, sin conexiones entrantes, reglas por dominio o dirección) y restricciones que podés fijar por app: sin cámara, sin USB y sin sockets Bluetooth (en el kernel), sin micrófono (la guardia de PipeWire de LordOS más los nodos de captura de la placa de sonido), sin notificaciones y "sin acceso a tus archivos", que se aplica desde el próximo inicio. No cubren el portapapeles, el Bluetooth a través de BlueZ en el bus del sistema ni los programas iniciados fuera del lanzador de apps. Solo las apps `.lpk` propias de LordOS tienen la caja de arena completa.
-**¿Una app de Linux puede ver otras ventanas o grabar la pantalla?** No a través de LordOS. El compositor solo le da a una app sus propias superficies y no ofrece ningún protocolo de captura de pantalla, no hay servidor X ni portal de captura de pantalla, y a una app restringida también se le niega el dispositivo de framebuffer, así que las ventanas protegidas como Contraseñas también quedan a salvo de ellas.
+**¿Una app de Linux puede ver otras ventanas o grabar la pantalla?** No a través de LordOS. El compositor solo le da a una app sus propias superficies y no ofrece ningún protocolo de captura de pantalla, las apps X11 solo ven otras apps X11 (nunca las apps Wayland ni a LordOS), no hay portal de captura de pantalla, y a una app restringida también se le niega el dispositivo de framebuffer, así que las ventanas protegidas como Contraseñas también quedan a salvo de ellas.
-**¿Y las apps que solo usan X11?** Todavía no funcionan: Xwayland no es parte de LordOS 0.8.2 Beta. Está planeado antes de la 1.0, con las apps X11 con la misma identidad por app, el mismo firewall y las mismas restricciones. Las apps GTK y Qt actuales hablan Wayland, y también el juego SDL que se probó.
+**¿Y las apps que solo usan X11?** Desde LordOS 0.8.3 Beta se abren con Xwayland, que arranca solo cuando una se conecta, con el marco de ventana del tema, su ícono en el Dock y el portapapeles compartido. Tienen la misma identidad por app, el mismo firewall y la misma atribución en el Monitor que las apps Wayland; las apps con restricciones de dispositivos o de archivos no reciben pantalla X. Se probaron XTerm, una app Java Swing y un juego SDL.
**¿Y Flatpak?** LordOS no lo usa ni lo integra, y no se probó.
@@ -63,8 +63,8 @@ Ausente a propósito: cualquier protocolo que le permita a una app capturar la p
## Límites honestos
-- **Todavía sin Xwayland** (planeado antes de la 1.0), así que no hay apps que usen solo X11.
-- **Todavía no:** arrastrar y soltar entre apps, la selección primaria con clic del medio, los métodos de entrada de LordOS (coreano, japonés, chino) dentro de las apps de Linux, y los pedidos de activación de apps.
+- **Las apps X11 se ven entre sí,** como en cualquier escritorio X11; se ven nítidas solo al 100 % de escala.
+- **Todavía no:** arrastrar y soltar entre apps, los métodos de entrada de LordOS (coreano, japonés, chino) dentro de las apps de Linux, y los pedidos de activación de apps.
- **Íconos solo en SVG:** LordOS todavía no dibuja SVG. Usa los íconos PNG que publica Debian para la mayoría de las apps, o la inicial.
- **Las apps de terminal** con archivo `.desktop` no aparecen en el lanzador de apps; arrancalas desde la Terminal.
- **Las apps GTK 3 mantienen su propio acento azul;** la lectura del esquema de colores desde el portal en Qt 6 no se probó.
diff --git a/web/content/features/linux-apps.pt.md b/web/content/features/linux-apps.pt.md
index 4b7c5c9..4360a4a 100644
--- a/web/content/features/linux-apps.pt.md
+++ b/web/content/features/linux-apps.pt.md
@@ -53,9 +53,9 @@ Ausente de propósito: qualquer protocolo que permita a um app capturar a tela o
**Os apps Linux ficam em sandbox?** Não por padrão. Isso é importante: eles rodam como o seu usuário, como em qualquer sistema Debian, e podem ler sua pasta pessoal. O que o LordOS acrescenta é um cgroup por app, a atribuição no Monitor, o firewall por app aplicado pelo kernel (permitir, negar, só LAN, sem conexões de entrada, regras por domínio ou endereço) e restrições que você pode definir por app: sem câmera, sem USB e sem sockets Bluetooth (no kernel), sem microfone (o guarda do PipeWire do LordOS mais os nós de captura da placa de som), sem notificações e "sem acesso aos seus arquivos", aplicada a partir da próxima abertura. Elas não cobrem a área de transferência, o Bluetooth através do BlueZ no barramento do sistema nem programas iniciados fora do lançador de apps. Só os apps `.lpk` do próprio LordOS recebem o sandbox completo.
-**Um app Linux consegue ver outras janelas ou gravar a tela?** Não pelo LordOS. O compositor só entrega a um app as superfícies dele mesmo e não oferece nenhum protocolo de captura de tela, não há servidor X nem portal de captura de tela, e um app restrito também tem o dispositivo de framebuffer negado, então janelas protegidas como a de Senhas também ficam privadas para eles.
+**Um app Linux consegue ver outras janelas ou gravar a tela?** Não pelo LordOS. O compositor só entrega a um app as superfícies dele mesmo e não oferece nenhum protocolo de captura de tela, apps X11 só veem outros apps X11 (nunca os apps Wayland nem o LordOS), não há portal de captura de tela, e um app restrito também tem o dispositivo de framebuffer negado, então janelas protegidas como a de Senhas também ficam privadas para eles.
-**E os apps que só falam X11?** Ainda não rodam: o Xwayland não faz parte do LordOS 0.8.2 Beta. Ele está planejado antes da 1.0, com os apps X11 ganhando a mesma identidade por app, o mesmo firewall e as mesmas restrições. Os apps GTK e Qt atuais falam Wayland, e o jogo SDL testado também.
+**E os apps que só falam X11?** Desde o LordOS 0.8.3 Beta eles abrem pelo Xwayland, que só inicia quando um deles se conecta, com a moldura de janela do tema, o ícone no Dock e a área de transferência compartilhada. Eles têm a mesma identidade por app, o mesmo firewall e a mesma atribuição no Monitor que os apps Wayland; apps com restrições de dispositivos ou de arquivos não recebem tela X. Foram testados o XTerm, um app Java Swing e um jogo SDL.
**E o Flatpak?** O LordOS não o usa nem o integra, e ele não foi testado.
@@ -63,8 +63,8 @@ Ausente de propósito: qualquer protocolo que permita a um app capturar a tela o
## Limites honestos
-- **Ainda sem Xwayland** (planejado antes da 1.0), então nada de apps só X11.
-- **Ainda não:** arrastar e soltar entre apps, a seleção primária do clique do meio, os métodos de entrada do LordOS (coreano, japonês, chinês) dentro dos apps Linux e os pedidos de ativação de apps.
+- **Apps X11 se veem entre si,** como em qualquer desktop X11; ficam nítidos só em 100 % de escala.
+- **Ainda não:** arrastar e soltar entre apps, os métodos de entrada do LordOS (coreano, japonês, chinês) dentro dos apps Linux e os pedidos de ativação de apps.
- **Ícones só em SVG:** o LordOS ainda não desenha SVG. Ele usa os ícones PNG que o Debian publica para a maioria dos apps, ou a inicial.
- **Apps de terminal** com arquivo `.desktop` não aparecem no lançador de apps; inicie-os pelo Terminal.
- **Os apps GTK 3 mantêm o próprio destaque azul;** a leitura do esquema de cores pelo portal no Qt 6 não foi testada.
diff --git a/web/content/legal/issues.en.md b/web/content/legal/issues.en.md
index 122ce0e..d62aa49 100644
--- a/web/content/legal/issues.en.md
+++ b/web/content/legal/issues.en.md
@@ -13,7 +13,7 @@ Before you write, check the [FAQ](/faq/) and, once they are public, the existing
## What to include in a bug report
-- **The LordOS version**, as shown in the About LordOS app (for example "0.8.2 · Beta").
+- **The LordOS version**, as shown in the About LordOS app (for example "0.8.3 · Beta").
- **How you installed it:** the ISO (live or installed), the Raspberry Pi 5 image, or the `.deb` on Debian 13.
- **Your hardware:** the computer or board model, the graphics card, the amount of memory, and any device involved (printer, touchpad, Wi-Fi adapter, monitor).
- **Steps to reproduce:** what you did, one step per line, starting from a fresh start if you can.
diff --git a/web/content/legal/issues.es.md b/web/content/legal/issues.es.md
index fc1c182..a2d86f7 100644
--- a/web/content/legal/issues.es.md
+++ b/web/content/legal/issues.es.md
@@ -13,7 +13,7 @@ Antes de escribir, revisá las [preguntas frecuentes](/faq/) y, cuando sean púb
## Qué incluir en un reporte de error
-- **La versión de LordOS**, como aparece en la app Acerca de LordOS (por ejemplo "0.8.2 · Beta").
+- **La versión de LordOS**, como aparece en la app Acerca de LordOS (por ejemplo "0.8.3 · Beta").
- **Cómo la instalaste:** la ISO (live o instalada), la imagen para Raspberry Pi 5 o el `.deb` en Debian 13.
- **Tu hardware:** el modelo de la computadora o de la placa, la placa de video, la memoria y cualquier dispositivo que tenga que ver (impresora, touchpad, adaptador Wi-Fi, monitor).
- **Pasos para reproducirlo:** qué hiciste, un paso por línea, desde un arranque limpio si podés.
diff --git a/web/content/legal/issues.pt.md b/web/content/legal/issues.pt.md
index b6c3d7c..d47faec 100644
--- a/web/content/legal/issues.pt.md
+++ b/web/content/legal/issues.pt.md
@@ -13,7 +13,7 @@ Antes de escrever, veja as [perguntas frequentes](/faq/) e, quando forem públic
## O que incluir num relato de bug
-- **A versão do LordOS**, como aparece no app Sobre o LordOS (por exemplo "0.8.2 · Beta").
+- **A versão do LordOS**, como aparece no app Sobre o LordOS (por exemplo "0.8.3 · Beta").
- **Como você instalou:** a ISO (live ou instalada), a imagem para Raspberry Pi 5 ou o `.deb` no Debian 13.
- **O seu hardware:** o modelo do computador ou da placa, a placa de vídeo, a quantidade de memória e qualquer dispositivo envolvido (impressora, touchpad, adaptador Wi-Fi, monitor).
- **Passos para reproduzir:** o que você fez, um passo por linha, a partir de uma inicialização limpa se possível.
diff --git a/web/content/legal/security.en.md b/web/content/legal/security.en.md
index 8a96af2..7b7b65e 100644
--- a/web/content/legal/security.en.md
+++ b/web/content/legal/security.en.md
@@ -6,7 +6,7 @@ Write to us through **[our contact form](https://www.iperfex.com/contacto/?lang=
Include, as far as you can:
-- the LordOS version (shown in the About LordOS app, for example "0.8.2 · Beta") and whether it is the ISO, the Raspberry Pi image or the Debian package;
+- the LordOS version (shown in the About LordOS app, for example "0.8.3 · Beta") and whether it is the ISO, the Raspberry Pi image or the Debian package;
- the component affected (for example the compositor, the app sandbox, the per-app firewall, remote desktop, the password vault, the Store, the Debian installer script or the website);
- the steps to reproduce it, a proof of concept if you have one, and the impact you see;
- how you'd like to be credited, if at all.
diff --git a/web/content/legal/security.es.md b/web/content/legal/security.es.md
index 594c17c..6df6c2d 100644
--- a/web/content/legal/security.es.md
+++ b/web/content/legal/security.es.md
@@ -6,7 +6,7 @@ Escribinos por **[nuestro formulario de contacto](https://www.iperfex.com/contac
Incluí, en la medida de lo posible:
-- la versión de LordOS (la ves en la app Acerca de LordOS, por ejemplo "0.8.2 · Beta") y si es la ISO, la imagen para Raspberry Pi o el paquete para Debian;
+- la versión de LordOS (la ves en la app Acerca de LordOS, por ejemplo "0.8.3 · Beta") y si es la ISO, la imagen para Raspberry Pi o el paquete para Debian;
- el componente afectado (por ejemplo el compositor, el aislamiento de apps, el firewall por app, el escritorio remoto, la bóveda de contraseñas, la Tienda, el script de instalación para Debian o el sitio);
- los pasos para reproducirlo, una prueba de concepto si la tenés, y el impacto que ves;
- cómo te gustaría que te mencionemos, si querés que lo hagamos.
diff --git a/web/content/legal/security.pt.md b/web/content/legal/security.pt.md
index 460b155..02e8d2f 100644
--- a/web/content/legal/security.pt.md
+++ b/web/content/legal/security.pt.md
@@ -6,7 +6,7 @@ Escreva pelo **[nosso formulário de contato](https://www.iperfex.com/contacto/?
Inclua, na medida do possível:
-- a versão do LordOS (no app Sobre o LordOS, por exemplo "0.8.2 · Beta") e se é a ISO, a imagem para Raspberry Pi ou o pacote do Debian;
+- a versão do LordOS (no app Sobre o LordOS, por exemplo "0.8.3 · Beta") e se é a ISO, a imagem para Raspberry Pi ou o pacote do Debian;
- o componente afetado (por exemplo o compositor, o sandbox de apps, o firewall por app, a área de trabalho remota, o cofre de senhas, a Loja, o script de instalação para Debian ou o site);
- os passos para reproduzir, uma prova de conceito se você tiver, e o impacto que você vê;
- como você gostaria de ser creditado, se quiser.
diff --git a/web/i18n/en.json b/web/i18n/en.json
index 6753f37..00511f2 100644
--- a/web/i18n/en.json
+++ b/web/i18n/en.json
@@ -17,7 +17,7 @@
"navDownload": "Download",
"navSupport": "Support",
"navAbout": "About",
- "badge": "Version 0.8.2 · Beta",
+ "badge": "Version 0.8.3 · Beta",
"heroTitle": "The free, fast and secure Linux desktop.",
"heroLead": "LordOS is a free GNU/Linux distribution based on Debian with its own desktop environment, display server and Wayland compositor written in C, its own interface engine, and native apps made to feel calm, clear and private.",
"ctaDownload": "Download LordOS",
diff --git a/web/i18n/es.json b/web/i18n/es.json
index 41c903c..cbdc40a 100644
--- a/web/i18n/es.json
+++ b/web/i18n/es.json
@@ -17,7 +17,7 @@
"navDownload": "Descargar",
"navSupport": "Apoyar",
"navAbout": "Nosotros",
- "badge": "Versión 0.8.2 · Beta",
+ "badge": "Versión 0.8.3 · Beta",
"heroTitle": "El escritorio Linux libre, rápido y seguro.",
"heroLead": "LordOS es una distribución GNU/Linux libre basada en Debian con su propio entorno de escritorio, servidor gráfico y compositor Wayland escritos en C, su propio motor de interfaz y apps nativas pensadas para sentirse tranquilas, claras y privadas.",
"ctaDownload": "Descargar LordOS",
diff --git a/web/i18n/pt.json b/web/i18n/pt.json
index 025ad8b..2a2a600 100644
--- a/web/i18n/pt.json
+++ b/web/i18n/pt.json
@@ -17,7 +17,7 @@
"navDownload": "Baixar",
"navSupport": "Apoiar",
"navAbout": "Sobre",
- "badge": "Versão 0.8.2 · Beta",
+ "badge": "Versão 0.8.3 · Beta",
"heroTitle": "O desktop Linux livre, rápido e seguro.",
"heroLead": "LordOS é uma distribuição GNU/Linux livre baseada no Debian com ambiente de desktop, servidor gráfico e compositor Wayland próprios, escritos em C, motor de interface próprio e apps nativos pensados para ser calmos, claros e privados.",
"ctaDownload": "Baixar LordOS",