"[libseat/backend/seatd.c:70] Could not connect to socket /run/seatd.sock: no such file or directory" after updating wlroots, Sway and libseat on Arch

Question

I just updated my system, there were only three updates available: wlroots, sway and libseat.

I don't have a display manager installed and before loading Sway I'm shown this:

[wlr] [libseat] [libseat/backend/seatd.c:70] Could not connect to socket /run/seatd.sock: no such file or directory

I've never had such an error before.

You should add this as an answer instead of a comment, as it solves your problem. Thanks btw! — CyanoKobalamyne, Jul 06 '21 at 11:08

score 6 · Accepted Answer · answered Jul 08 '21 at 21:54

6

Problem solved by adding LIBSEAT_BACKEND=logind to my /etc/environment file. I don't know if it's the correct way to fix the warning message but it worked. It seems like wlroots dropped logind dependency and rely on libseat for seat management. I learned this from a user in the Arch room on Matrix.

answered Jul 08 '21 at 21:54

With https://git.sr.ht/~kennylevinsen/seatd/commit/36f54adc2c1b16943e5470af3ad85d2b4cdf480c this should no longer be an error and so the workaround should no longer be necessary with the next release – carloabelli Jul 09 '21 at 01:16
carloabelli above is right - after switching to `seatd-git` from the AUR instead of just `seatd` there's no need to add anything to the environment – walnut_salami Jul 31 '21 at 12:42
This does not work for me, now I get "no logind backend"... – Oliv Oct 12 '21 at 15:28
Is there a way to configure a seat in a script file or is it just a kind of in theory open but factualy closed IBM secret? – Oliv Oct 12 '21 at 15:34
This was still needed on my Arch Linux with `[email protected]`, `[email protected]`, otherwise it throws the error from the OP. – tukusejssirs Dec 06 '22 at 14:07

"[libseat/backend/seatd.c:70] Could not connect to socket /run/seatd.sock: no such file or directory" after updating wlroots, Sway and libseat on Arch

1 Answers1