On the desktop

What you get installed

The desktop is set up before you log in for the first time: Hyprland with Dux Shell, a greeter that matches it, and GTK and Qt colors that matugen takes from your wallpaper. A media player, a package manager, a browser and a terminal are installed alongside them, so the machine is usable the moment you sit down. There is no theming left for you to do.

The Aelum wallpaper and colors settings on the Aelum desktop
The wallpaper and colors settings on a fresh install: the wallpaper and its fill mode, light or dark theme mode, and dynamic colors driven by the wallpaper. This is already set up before your first login.

Hyprland

Dynamic tiling Wayland compositor.

Dux Shell

A complete Quickshell-based desktop shell.

Dux Greeter

A fast login screen that matches the desktop theme.

GTK + Qt theming

Your apps pick up the current palette without you configuring them.

Aelum splash

The branded Plymouth boot screen, which also asks for your LUKS passphrase.

Packages

Aelum's package manager: browse, install, update and build AUR packages in a window.

Videos

Aelum's media player: GTK4 and libadwaita over mpv, following the desktop's palette.

Firefox

The browser that ships here, themed to match the desktop.

Screenshots

Screenshots from the installed system

These are captures of an actual install. The same palette runs through the settings, the terminal and the rest of the desktop.

The Aelum app launcher with the apps that ship installed
The app launcher: press Super + Space and start typing. A handful of apps come preinstalled — files, browser, editor, media player, terminal.
fastfetch output in the foot terminal on the Aelum desktop
fastfetch in foot: one command that prints what the machine is — OS, kernel, package count, CPU, GPU, memory and disk usage.
The Dux Shell control center on the Aelum desktop, open on its weather page
The control center — one window with tabs for overview, media, wallpapers, weather and digital wellbeing. This one is open on the weather tab.
The Aelum settings window, open on its bar settings
The settings window, where you can customize the look and feel however you want.
The installed system

What the installed system does

Once the install finishes, your machine keeps doing its part: on a btrfs install it takes a snapshot around every pacman transaction, the desktop colors itself from your wallpaper, and the system boots with its own entry in the rEFInd menu. The graphics driver is chosen for your card, the repositories are already configured, and the applications Aelum ships are updated by the same command as everything else. All of that is configured already, so there is nothing left to set up.

Snapshots you can go back to

On a btrfs install, every pacman transaction takes a snapshot before and after it. From the Aelum entry in the rEFInd menu you can start an older state, and snapper rollback makes it the system again.

Colors taken from your wallpaper

matugen reads your wallpaper and re-themes the shell and your GTK and Qt apps to match it. Dark, light or automatic — choose a wallpaper and the rest of the desktop follows.

Disk encryption with one passphrase

If you choose LUKS2 during the install, the only thing you do differently afterwards is type your passphrase into the boot splash.

Volumes you can resize later

Turn on LVM on the disk screen and the System partition becomes one volume group holding two logical volumes, root and home, so space between them is yours to move later. Booting is unchanged: the fstab and the boot entries still name filesystem UUIDs, and LUKS still sits below LVM when you choose both.

A branded boot menu and splash

You get an Aelum rEFInd menu and Plymouth splash instead of boot messages. Each Aelum install on the disk keeps its own boot entry and its own snapshot submenu, so they don't overwrite each other.

Defaults that are already set

PipeWire for audio, zram instead of a swap file, and Firefox themed to match the desktop. There is no list of setup steps left for you to do.

The graphics driver your card needs

Before it installs any graphics package, the installer reads the PCI bus and picks the matching driver set: Mesa and its Vulkan driver for AMD and Intel, the open NVIDIA driver for a Turing-or-newer card, vulkan-nouveau for older NVIDIA, and a software driver for a virtual machine. Every set carries the 32-bit Vulkan driver as well, so nothing on your system stops later to ask which driver you meant.

32-bit software installs without setup

Arch keeps Steam, Wine and their 32-bit libraries in a repository called multilib, which a stock pacman.conf ships commented out. The installer turns it on, so a fresh system installs those programs with no hand-editing — and the driver set the installer picks for your card already answers the 32-bit Vulkan dependency they pull in.

Aelum's own apps arrive through pacman

The installer enables the [aelum] repository in pacman.conf and trusts the release key that signs it, so the distro's applications — the media player and the package manager — install and update with the same command as everything else. Everything in that repository is signed with the same key as the ISO and served from the same CDN as the releases.

Get started

Ready to install Aelum?

Download the ISO, write it to a USB stick, and boot from it. You need no internet for the install, and it takes less than 2 minutes.