You are not logged in.
- Topics: Active | Unanswered
#1 2026-05-19 20:21:14
- thes3pt3mb3r
- Member
- Registered: 2026-04-11
- Posts: 12
[SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start
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.
Offline
#2 2026-05-19 22:22:19
- ralph.ronnquist
- Administrator
- From: Battery Point, Tasmania, AUS
- Registered: 2016-11-30
- Posts: 1,685
Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start
Presumably it means that there is a seatd running that uses that socket pathname.
Offline
#3 2026-05-20 07:06:24
- thes3pt3mb3r
- Member
- Registered: 2026-04-11
- Posts: 12
Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start
Yes,I know this much but the problem is that this message shows and compositor does not start.
Last edited by thes3pt3mb3r (2026-05-20 07:07:40)
Offline
#4 2026-05-20 10:33:43
- ralph.ronnquist
- Administrator
- From: Battery Point, Tasmania, AUS
- Registered: 2016-11-30
- Posts: 1,685
Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start
Why do you want to use the command seatd-launch dwl.
Is seatd running already?
Is there a dwl running already?
Offline
#5 2026-05-20 14:30:59
- thes3pt3mb3r
- Member
- Registered: 2026-04-11
- Posts: 12
Re: [SOLVED] Socket file found at socket path /run/seatd.sock, refusing to start
Sorry,It was my mistake becouse I have always used seatd like that and did not check 'dwl' by itself.
Offline
