Ferdinand Bachmann

Hi! Thanks for the report! This looks at first glance like either a bug in grim or a bug in the compositor (I assume you are using Sway?). Grim is...

> Besides getting a lot of this below, there is nothing that tells me something. > > ``` > [ERROR] [wlr] [/usr/src/debug/wlroots/0.17.4-r0/backend/drm/atomic.c:73] connector VGA-1: Atomic commit failed: Device or resource...

Thanks for the log! It looks like `grim` correctly calls `copy()` on the screencopy frame, but the compositor never finishes and doesn't send the `ready()` event. This looks like it's...

Hi! sorry, I didn't get to looking at this in detail. I didn't find anything obvious in the wlroots codebase at that commit and I also wasn't able to reproduce...

I recommend potentially opening an issue with wlroots, since the screencopy `ready` event is never sent.

> Only a single `wl_output` is advertised to clients, so that layer-shell works as expected. Each output can still have different settings (scale, transform, refresh rate, color management, etc). >...

Hi! if wl-mirror stops mirroring then it probably died. does wl-mirror print anything useful on stdout/stderr? You can also add `--verbose` to your wl-mirror call to get extra log output....

Thanks for the logs! This appears to be some kind of issue with DMA-BUF import/export in combination with software rendering, though I'm not sure who is at fault here. The...

> Good morning, Good morning! > `-b screencopy` works, but unfortunately this is unusable because it's really extremely slow... Yeah, screencopy with SHM buffers isn't really intended for continuous video...

Thanks for the info! Under my current setup my wlroots doesn't seem to like to be started with `LIBGL_ALWAYS_SOFTWARE`, so I will need to check what's wrong before I can...