Desktop overview
The UFLinux desktop is a Wayland session assembled from a small number of components, each chosen or written for a specific job. It has no GNOME or KDE dependencies.
The stack
Section titled “The stack”| Layer | Component |
|---|---|
| Compositor | labwc |
| Panel / taskbar | uflinux-desktop, a resident GTK4 process written for UFLinux |
| Start menu | the same uflinux-desktop process |
| Settings UI | uflinux-settings, plain GTK4 |
| Session service | uflinux-settingsd, headless GLib/GIO |
| Privileged helper | uflinux-settings-system, root D-Bus + polkit |
| Greeter | ReGreet with the adw-gtk3 dark theme |
| Terminal | Foot |
| File manager | UFLinux Files (uflinux-files, from the apps repository) |
| Notifications | Mako |
| Audio | PipeWire and WirePlumber, with pipewire-pulse |
| Networking | ConnMan with iwd |
| Power | TLP, plus a BusyBox acpid power-button hook |
| Time sync | ConnMan’s SNTP client |
Settings and the desktop shell are Rust workspaces using plain GTK4 and the user’s GTK
theme. Neither depends on libadwaita, GNOME Settings, or the GNOME settings daemon. The
Start menu is compiled into the uflinux-desktop binary, so the taskbar and the menu are
one process.
Session start
Section titled “Session start”OpenRC starts independent services in parallel for both live and installed systems.
uflinux-defaults sets rc_parallel="YES" in /etc/rc.conf.d/uflinux.conf; service
dependencies still determine ordering. Set rc_parallel="NO" in that file when
diagnosing a boot problem — the change takes effect on the next boot and survives
upgrades.
ReGreet starts the UFLinux session directly. There is no session selector. The unified
desktop is the default session: uflinux-autostart starts uflinux-desktop --supervise,
which keeps the resident shell running. The Start menu starts hidden with its widgets,
layout and application catalog already prepared, so opening it is fast.
Renderer selection
Section titled “Renderer selection”The session wrapper probes hardware Vulkan, then hardware OpenGL, then pixman. It skips Vulkan on Sandy Bridge, Ivy Bridge and Bay Trail Intel graphics, where Vulkan support is incomplete, and it skips software Vulkan entirely. Explicit renderer overrides are respected, and startup fallback attempts are limited.
A normal logout — or a crash after the desktop has started — does not restart the session with a different renderer. On software rendering, GTK uses Cairo unless you override it, and the quick-settings cards drop their blurred shadow to reduce software-rendering allocations.
Installed applications
Section titled “Installed applications”Every architecture ships:
- Firefox with uBlock Origin
- Foot terminal
- Loupe image viewer and htop
- Celluloid media player
- Transmission BitTorrent client
- Mako notifications
- GNOME Disks and File Roller for images and archives
- gpu-screen-recorder as the screenshot and screen-recording backend
- BlueZ for Bluetooth and ConnMan’s VPN daemon for WireGuard tunnels
UFLinux Files (uflinux-files) comes from the apps repository, which indexes only
x86_64, aarch64, ppc64le and riscv64 — x86 and armv7 ship without a graphical
file manager rather than with an unsatisfiable dependency. There is no remote-desktop
service enabled by default.
Memory
Section titled “Memory”The installed desktop is built and accepted against a reference target of 512 MiB of RAM, one display, and no swap. The live image is a different story: it unpacks the desktop and the full Papirus icon theme into a tmpfs root whose default capacity is 75% of RAM, so live sessions need at least 4 GiB.
Background components are budgeted at ≤16 MiB PSS, the full Settings UI at ≤80 MiB, and the flyout at ≤64 MiB. See Validation record for measured numbers.
Taskbar layout
Section titled “Taskbar layout”The taskbar carries the Start button, pinned favourites and running-window groups, the tray, and separate Network, Sound and Power buttons with symbolic icons that track connection state, output volume and battery. Desktop machines show a bolt instead of a battery. Buttons can be pinned, reordered by dragging, and previewed on hover; the clock opens a calendar with a notification centre. StatusNotifier icons from background apps sit behind a single chevron so they cannot push the clock off a narrow panel.
Details in Start menu and UFLinux Settings.
Derived from README.md inUFlinux-project/uflinux3(b4f4817). Report documentation problems inUFlinux-project/docs.