Dev1 Galaxy Forum / [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

dummy@example.com (thes3pt3mb3r) — Wed, 20 May 2026 14:30:59 +0000

Sorry,It was my mistake becouse I have always used seatd like that and did not check 'dwl' by itself.

Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

dummy@example.com (ralph.ronnquist) — Wed, 20 May 2026 10:33:43 +0000

Why do you want to use the command seatd-launch dwl.
Is seatd running already?
Is there a dwl running already?

Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

dummy@example.com (thes3pt3mb3r) — Wed, 20 May 2026 07:06:24 +0000

Yes,I know this much but the problem is that this message shows and compositor does not start.

Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

dummy@example.com (ralph.ronnquist) — Tue, 19 May 2026 22:22:19 +0000

Presumably it means that there is a seatd running that uses that socket pathname.

[SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start

dummy@example.com (thes3pt3mb3r) — Tue, 19 May 2026 20:21:14 +0000

Command 'ls -l' on /etc/seatd* showed that /run/seatd.sock is owned by root and video group. User is in video group,yet I still get 'Socket file found at socket path /run/seatd.sock, refusing to start' after running 'seatd-launch dwl'. That message is not really telling me much.