Skip to content

Sov error using displaying almost nothing #70

@turip0

Description

@turip0
Image

I have used sov before with no errors and recently I had a bug with another program (wob) which it didn't delete $SWAYSOCK.wob. So I stupidly added in my sway startup config: exec rm -rf /run/user/1000/sway-ipc* . I was not aware that other programs used that aswell. On the next boot I got no workspaces (as shown in the image) but the demon was running. I have reinstalled sov and tried to reconfigure systemd but in line "cp contrib/systemd/sov.{service,socket} ~/.local/share/systemd/user/" I get error:
cp: cannot stat 'contrib/systemd/sov.service': No such file or directory cp: cannot stat 'contrib/systemd/sov.socket': No such file or directory
In my config I have:
exec rm -f /tmp/sovpipe && mkfifo /tmp/sovpipe && tail -f /tmp/sovpipe | sov -t 200 --holdkey=65515
Also if I manually pkill sov and run it from terminal I get the error:
00:00:00.000 [common/ipc-client.c:66] Unable to connect to /run/user/1000/sway-ipc.1000.641.sock 00:00:00.000 [common/ipc-client.c:66] Unable to connect to /run/user/1000/sway-ipc.1000.641.sock
as shown in the photo.

How can I fix the issue?? Also is there another way to only remove $SWAYSOCK.wob manually so that both programs can run semoultaniously??

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions