Austin Shafer

Could you please provide the information I mentioned in the previous comment? I haven't used labwc myself but wlroots-based compositors need the `WLR_NO_HARDWARE_CURSORS=1` environment variable on Nvidia devices.

Thanks for the detailed report, do you know if this reproduces only on Wayland or on Xorg as well?

Are you able to provide the app you're seeing this with?

We are aware of the blocking behavior here, but it requires significant work and is not a trivial fix. Unfortunately we do not have an expected timeline for the fix...

If it works in 1.1.13 and doesn't work with the latest do you know what commit caused it? If not I can reproduce and bisect.

Do you have an easier reproduction app than looking glass? Something where I don't have to set up an entire VM to reproduce this? How much time is "a short...

Thanks for the details, unfortunately I couldn't find anything obviously incorrect and it looks like we are still sending valid buffers. There is one spot in the [middle](https://gist.github.com/blackxored/2950e31091c85d2e4f4611ae03d3cc5e#file-gistfile1-txt-L3154) where it...

It still reproduces with explicit sync disabled? Either Gnome or Plasma are good comparisons. I've run sway fine with proprietary drivers using the vulkan renderer and disabling hw cursors.

This looks like a different issue: ``` [4097624.614] {Display Queue} wl_display#1.error(wp_linux_drm_syncobj_surface_v1#57, 5, "explicit sync is used, but no release point is set") wp_linux_drm_syncobj_surface_v1#57: error 5: explicit sync is used, but...

[This](https://github.com/amshafer/nvidia-driver/commit/455d88859fb003bfdcdd9da070cd0ebeecb2d514) commit in `520.60.11` should fix the build issue you saw. Do you know what branch you are on? You should use `520.60.11`. I updated the default branch to that...