-
Notifications
You must be signed in to change notification settings - Fork 56
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
Failed to receive answer: io error: Resource temporarily unavailable (os error 11) when plugging or unplugging display #26
Comments
I did a bit more investigation and, after adding a new display, a debug output gets printed: The process (in no-daemon mode) seems to be stuck in a syscall. |
Hello. Thanks for the detailed report! Really sorry for the time it took me to respond. Unfortunately, I am still really full of stuff for this and next week, so it might take a while until I have a more thorough look at this. I do want to solve it as fast as possible, since it must make using |
I managed to get a stack trace of the daemon before and after unplugging the monitor. It confirms the fact that it hangs at a futex syscall. Normal stack trace Ps. Also using Arch with Sway as the compositor. |
I'm having this issue, but for me it happens when my system idles. Using swayidle, I'm calling for my monitor to go into power-saving mode. |
I tried the patch and it seems to work very nicely :) |
Thanks for confirming! I always like to leave things running in my machine for a couple of days before merging, just to make sure nothing explodes when using it for real. |
I'm running swww version 0.4.3 on Arch, using Sway as the compositor.
Running sway init and then setting an image as the background works, when using my laptop display alone, or using my laptop's display plus an external display that is plugged in.
However, when the swww daemon is running and I plug / unplug the display, the daemon gets into a state where it can not be communicated with.
Setting the background with:
swww img --transition-speed=1 --transition-step=1 ~/Pictures/my_wallpaper.png
results in:
Failed to receive answer: io error: Resource temporarily unavailable (os error 11)
Running swww kill results in the same error.
I can only get it running again by killing the process, and removing the socket manually.
The text was updated successfully, but these errors were encountered: