You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a command without first initializing the daemon you get this error message. Error: "Failed to connect to socket: No such file or directory (os error 2)"
It's not immediately obvious what the problem is.
I think it would be helpful if a suggestion to check if the daemon is running was added (as a second line maybe?).
Something like this could work. Is the swww daemon running?
The text was updated successfully, but these errors were encountered:
When running a command without first initializing the daemon you get this error message.
Error: "Failed to connect to socket: No such file or directory (os error 2)"
It's not immediately obvious what the problem is.
I think it would be helpful if a suggestion to check if the daemon is running was added (as a second line maybe?).
Something like this could work.
Is the swww daemon running?
The text was updated successfully, but these errors were encountered: