No description
Find a file
2025-10-18 20:36:37 +02:00
.builds ci: Use meson setup in all CI scripts 2025-02-24 22:10:16 +01:00
common Merge remote-tracking branch 'origin/master' into obsd 2025-10-18 20:36:37 +02:00
contrib/systemd systemd: restrict access to devices 2023-12-31 01:09:57 +01:00
examples/simpletest examples/simpletest: check for libseat_dispatch failures 2021-09-22 21:59:41 +02:00
include seatd: Add support for hidraw devices 2024-10-14 20:30:00 +02:00
libseat seatd: Add validation of device path libseat/seatd: Add validation of seat_name 2024-10-30 19:37:59 +01:00
man man: add missing arg in -n syntax 2023-01-28 23:10:29 +01:00
seatd Merge remote-tracking branch 'origin/master' into obsd 2025-10-18 20:36:37 +02:00
seatd-launch seatd-launch: Avoid argv[0] in help text 2022-05-23 22:03:38 +02:00
tests Merge remote-tracking branch 'origin/master' into obsd 2024-07-10 15:32:46 +02:00
.clang-format clang-format: Fix alignment 2021-09-21 12:48:24 +02:00
.editorconfig Add .editorconfig 2021-09-02 20:41:47 +02:00
LICENSE Add LICENSE 2020-07-31 01:34:04 +02:00
meson.build Merge remote-tracking branch 'origin/master' into obsd 2025-10-18 20:36:37 +02:00
meson_options.txt build: add prefix to libseat options 2021-07-06 22:11:43 +02:00
README.md readme: Minor rewording 2024-12-05 16:03:57 +01:00

seatd and libseat

A minimal seat management daemon, and a universal seat management library.

Currently supports Linux and FreeBSD, and has experimental NetBSD support.

What is seat management?

Seat management takes care of mediating access to shared devices (graphics, input), without requiring the applications needing access to be root.

What's in the box?

seatd

A seat management daemon, that does everything it needs to do. Nothing more, nothing less. Depends only on libc.

libseat

A seat management library allowing applications to use whatever seat management is available.

Supports:

  • seatd
  • (e)logind
  • embedded seatd for standalone operation

Each backend can be compile-time included and is runtime auto-detected or manually selected with the LIBSEAT_BACKEND environment variable.

Which backend is in use is transparent to the application, providing a simple common interface.

Why not (e)logind?

systemd-logind is not portable, and being part of the systemd project, it cannot be used in an environment not based on or compatible with systemd.

elogind tries to isolate systemd-logind from systemd through brute-force. This requires actively fighting against upstream design decisions for deep integration, and the efforts must be repeated every time one syncs with upstream. And even after all this work, one is left with nothing but a hackjob.

Why spend time isolating logind and keeping up with upstream when we could instead create something better with less work?

Why does libseat support (e)logind?

In order to not be part of the problem. We will not displace systemd-logind anytime soon, so for user shells like sway, seatd joins the ranks of logind and direct session management for things they need to support.

Instead of giving user shell developers more work, libseat aims to make supporting seatd less work than what they're currently implementing. This is done by taking care of all the seat management needs with multiple backends, providing not only seatd support, but replacing the existing logind and direct seat management implementations.

How to discuss

Go to #kennylevinsen @ irc.libera.chat to discuss, or use ~kennylevinsen/seatd-devel@lists.sr.ht.