https://bugs.kde.org/show_bug.cgi?id=508822

Zamundaaa <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
             Status|REPORTED                    |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #2 from Zamundaaa <[email protected]> ---
This is the WAYLAND_DEBUG output of a single frame of that test app:

> [2477892.765] {mesa vk display queue}  -> 
> wp_linux_drm_syncobj_surface_v1#79.set_acquire_point(wp_linux_drm_syncobj_timeline_v1#99,
>  0, 2743)
> [2477892.769] {mesa vk display queue}  -> 
> wp_linux_drm_syncobj_surface_v1#79.set_release_point(wp_linux_drm_syncobj_timeline_v1#100,
>  0, 2743)
> [2477892.771] {mesa vk display queue}  -> wl_surface#4.attach(wl_buffer#97, 
> 0, 0)
> [2477892.774] {mesa vk display queue}  -> wl_surface#4.damage_buffer(0, 0, 
> 2147483647, 2147483647)
> [2477892.777] {mesa vk display queue}  -> wp_fifo_v1#80.set_barrier()
> [2477892.779] {mesa vk display queue}  -> wp_fifo_v1#80.wait_barrier()
> [2477892.782] {mesa vk display queue}  -> wl_surface#4.commit()
> [2477892.787] {mesa vk display queue} discarded wl_buffer#76.release()
> Frame time: 0
> [2477892.796] {Default Queue}  -> 
> zwp_pointer_constraints_v1#14.lock_pointer(new id zwp_locked_pointer_v1#104, 
> wl_surface#4, wl_pointer#41, nil, 2)
> [2477892.800] {Default Queue}  -> 
> zwp_locked_pointer_v1#104.set_cursor_position_hint(0.00000000, 0.00000000)
> [2477892.804] {Default Queue}  -> wl_surface#4.commit()
> [2477892.807] {Default Queue}  -> zwp_locked_pointer_v1#104.destroy()
> [2477892.943] {Display Queue} wl_display#1.delete_id(104)

The issue is that the commit for the pointer constraint clears the fifo
barrier, which it shouldn't do.

I'm not so sure SDL should be doing these commits either, but there's also
definitely a bug in KWin here.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to