Name: libseat
Version: 0.5.0-2

Error on linux console. Sway starts normally, but now issues this error:

$ sway
00:00:00.004 [ERROR] [wlr] [libseat] [libseat/backend/seatd.c:78] Could not connect to socket /run/seatd.sock: No such file or directory

Does libseat package come with seatd.service?
NO

Does libseat come with a custom startup script?
NO

Does seatd get started by some other service after a reboot?
NO

Let's try running "seatd -u nobody -g nobody" in another console, and retry sway. Does error go away?
NO

What are the socket perms?
srwxrwx--- 1 nobody nobody 0 Jun 28 06:03 seatd.sock

So the user and group perms *need* to be correct for this to work. Does the man page mention it?
NO

Any other libseat docu?
NO

Sway's?
NO

... Are you a machine that only answers "no"?
NO

So, you can answer "yes"?
YES

What does the seatd source say? Is there a service file?
YES

"ExecStart=seatd -g seat". Did libseat install group "seat" on my system?
NO

/etc/group LastMod March22. systemd-logind runs as root.root. So, no apparent group to run seatd as.
NO

If I add a seatd service file and group seat, do I know sway will use group seat permissions?
NO

Any sign my user account needs to add "seatd" as a supplementary group before I can login?
NO

Check the seatd AUR page (and the Gentoo Wiki). Any hint there?
NO

The source notes say it can outright replace system-logind. That's neat. Does it offer any list of features it duplicates? Any list it does *not* duplicate?
NO

And, of course, no Arch Wiki page.
NO

So no one thought this through before they pushed it?
NO