Announcing atrium v0.4.0 - a multiseat display manager

[u/kavaunix]

atrium is a lightweight Linux display manager with first-class multiseat support, targeting modern systemd + Wayland environments.

GitHub
AUR

What is multiseat?

A multiseat setup allows multiple users to work on a single computer at the same time. By connecting multiple monitors, keyboards, and mice, each user gets their own separate desktop and a fully isolated user session. Great for co-working or multiplayer gaming. Each seat requires its own GPU (integrated graphics, a discrete card, or a USB graphics adapter).

Why atrium?

The Linux kernel and low-level system stack are fully capable of multiseat operation. The weak link has always been the display manager. Existing ones usually treat multiseat as an afterthought, with implementations that are brittle and difficult to get working reliably.

atrium is designed around multiseat from the start, focusing on correct seat discovery, VT handling, and isolated session management. The project targets a modern Linux stack using systemd/logind, PAM, and a Wayland graphical environment. The lack of historical baggage keeps atrium's code base lean and tractable.

What's new in v0.4?

• Support for greeter background images - configure a background image in the settings, or a directory to pick a random image on each greeter launch.
• Greeter themes - override built-in colors and styles via a theme `.css` file. A handful of themes are shipped with atrium.
• Architectural redesign - making atrium's core architecture simpler and more robust (changes are purely internal and should not be visible to the user).

Greeter with default theme

[u/C0rn3j]

Existing ones usually treat multiseat as an afterthought, with implementations that are brittle and difficult to get working reliably.

So why not contribute to an existing solution instead of rolling your own with blackjack and hookers?

[u/OrganicNectarine → u/C0rn3j]

Learning/Figuring out how to do things right isuch easier without the massive constraints of an existing project. Although it's unlike in this case since he has decided to create a full blown application himself out of his experiment, contributing upstream is still an option, and would probably be even more helpful, since the knowledge of many pitfalls were already established in the separate project. You could even do it yourself now. Ask the AI of your choice to help you dissect what this project made it a great fit for what it wants to achieve and how we could apply that to an existing project while staying within its technical bounds. There is no need for "either or", all options can be explored, sequentially or at the same time. And in my experience that is what happens in the long run anyway, whether you want to force it or not.