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

Vlad Zahorodnii <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
                   |ma/kwin/-/commit/89c388a565 |ma/kwin/-/commit/fe60767f83
                   |8fbf48fd302fea707682abf23b4 |cd57f14f449768862be09e44a50
                   |c19                         |2a1

--- Comment #11 from Vlad Zahorodnii <[email protected]> ---
Git commit fe60767f83cd57f14f449768862be09e44a502a1 by Vlad Zahorodnii.
Committed on 28/05/2026 at 10:04.
Pushed by vladz into branch 'Plasma/6.7'.

xwayland: Send a SelectionNotify if there is no wayland source

If there is no wayland data source, the Selection may not send a
corresponding SelectionNotify event to let the client know about the
failure.

If the client doesn't know that the SelectionRequest has failed, it will
continue thinking that the data will arrive, and it can go pretty bad
with blocking api in QMimeData.

This change makes kwin sends a proper SelectionNotify event in response
to a SelectionRequest when there is no wayland data to pass.

I'm not entirely sure why the else branch of "event->time < m_timestamp"
sends no SelectionNotify event, my best guess it is to handle multiple
clipboard owners in the same process (which doesn't really matter to
kwin).
(cherry picked from commit 89c388a5658fbf48fd302fea707682abf23b4c19)

M  +6    -1    src/xwayland/selection.cpp

https://invent.kde.org/plasma/kwin/-/commit/fe60767f83cd57f14f449768862be09e44a502a1

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

Reply via email to