Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to oguri socket: No such file or directory #5

Open
I60R opened this issue Nov 25, 2021 · 1 comment
Open

Unable to connect to oguri socket: No such file or directory #5

I60R opened this issue Nov 25, 2021 · 1 comment
Assignees

Comments

@I60R
Copy link
Contributor

I60R commented Nov 25, 2021

This is displayed when spawning swayblur when oguri daemon isn't run. Maybe it would be better to spawn a new instance instead of printing the error?

Also, it seems that currently oguri conflicts with swaybg and it's a bit of a puzzle to figure this out, especially if the latter is launched through setting wallpaper in sway config. Although, it's not directly related to swayblur it could be handled here (by killing swaybg process) until it gets fixed upstream

@WillPower3309
Copy link
Owner

I'll add a section to this in the readme, but instead of having the line in your sway config setting the wallpaper it expects you to start the oguri daemon. I'll make that more clear and spawn an instance instead though

@WillPower3309 WillPower3309 self-assigned this Nov 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants