Seatd: Difference between revisions

Revision as of 03:34, 11 April 2025

Seatd is a seat management daemon, that does everything it needs to do. Nothing more, nothing less. Depends only on libc. Seat management takes care of mediating access to shared devices (graphics, input), without requiring the applications needing access to be root.

When using elogind, seatd is not required and viceversa. Don't add both to auto-start.

Note: Reading about seatd and elogind, you might get the impression that elogind is required for polkit. But seatd/polkit works fine if you use groups in the polkit rules, only for "subject.active" elogind is required. Which means with seatd you are restricted to YES or NO rules, no AUTH_ADMIN, since agents need POLKIT_IS_SUBJECT.

Installation

apk add seatd # install seatd rc-update add seatd # configure it to auto-start service seatd start # start it now adduser $USER seat # allow current user to access seatd

If you are already logged in as a $USER, you will need to relogin.

Configuration

Ensure that XDG_RUNTIME_DIR is set before starting your Wayland compositor.

@@ Line 18: / Line 18: @@
 Ensure that [[XDG_RUNTIME_DIR]] is set before starting your Wayland compositor.
-== Seatd and sway ==
-When using seatd, adding the following lines to {{Path|~/.profile}} or other shell specific profile file will launch Sway automatically with and [[D-Bus]] only in tty1. {{Cat|~/.profile|<nowiki>...
-#start sway with DBUS (only in tty1)
-if [ "$(tty)" = "/dev/tty1" ]; then
-     exec dbus-run-session sway
-fi
-...</nowiki>}}
-Instead of depending on {{Path|.profile}} or their equivalent files a [[Sway#Starting_sway|wrapper script]] can also be used.
 == See Also ==