Sending wallpapers to the daemon twice in quick succession makes all further respones fail about swww HOT 8 CLOSED

That's very interesting. Thank you for the through explanation! This will probably take me a little longer since it seems like a more involved problem than the previous one.

Meanwhile, you made me realize that's it's been a while since I did a release, and the current code has a lot more stuff than v0.3.0, so I went ahead and released v0.4.0 with all the newer improvements. I will most likely release 0.4.1 as soon as I manage to fix this.

from swww.

I tested the PR and can confirm that it fixes the issue.

from swww.

This is actually solved on master (I just fixed it). But master currently has some other problems. I'd suggest staying at 0.7.3 for now, until 0.8.1 is out (hopefully very soon).

from swww.

I also can't reproduce this error. Unlike #12, however, I don't actually know what might be causing this.

In particular, it shouldn't be possible for swww kill to fail while the daemon is running.

Can you please answer a few questions?

1. Are you using the latest version of swww?
2. Did you by any chance send images that need to be resized?
3. If you wait some time, does the image eventually appear on screen?

I am thinking that it might just be another issue of the timeout being too low. You send the image, it takes a while to process it, but the client doesn't wait and fails. You try to kill the daemon but it is STILL processing the image, so it fails again.

from swww.

Just like #12 it was mostly fixed by updating to the latest version.
The issue still remains with some WebP images though.

This one for example
https://files.catbox.moe/xi5toc.webp
It normally renders correctly and appears on screen without error.

When sent twice in quick succession it doesn't seem to appear at all and swww kill fails

from swww.

I should probably mention that I use two monitors, one 1440p and one 1080p, so the image does need resizing for one of the monitors.

After some testing with the --outputs flag I can only reproduce the error with this image when sending it to both outputs

It seems that it does appear on screen sometimes, but only on one monitor/output and it looks very weird.

from swww.

Hello, I just managed to reproduce it somewhat and made a PR that should have fixed. Could you please test it just to confirm it?

from swww.

I've been getting this error again since the new version 0.8.0

from swww.