Summary: | After drag-and-drop, all Xwayland apps stop reacting to mouse clicks until re-login or reboot | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Patrick Silva <bugseforuns> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexey-ilyin, dev+kde, nate |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kwin/commit/2d88ce5a5d156581ec9290823eb39bb8a47689a1 | Version Fixed In: | 5.24 |
Sentry Crash Report: |
Description
Patrick Silva
2022-01-30 11:26:56 UTC
In fact, all Xwayland apps (including Firefox) stop reacting to mouse clicks after the provided steps. A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1967 Git commit b1d0928c8e3464e5a1a519263c5af0ea37782f76 by David Redondo. Committed on 03/02/2022 at 14:01. Pushed by davidre into branch 'master'. xwayland: Handle drag being cancelled There was no handling for the drop being cancelled at all, leading to leaked WlVisit and XtoWlDrag objects. X clients could also be confused about the state of the drag and for example not being able to start another drag. M +5 -0 src/xwl/datasource.h M +7 -1 src/xwl/drag_x.cpp https://invent.kde.org/plasma/kwin/commit/b1d0928c8e3464e5a1a519263c5af0ea37782f76 Git commit 2d88ce5a5d156581ec9290823eb39bb8a47689a1 by David Redondo. Committed on 03/02/2022 at 14:23. Pushed by davidre into branch 'Plasma/5.24'. xwayland: Handle drag being cancelled There was no handling for the drop being cancelled at all, leading to leaked WlVisit and XtoWlDrag objects. X clients could also be confused about the state of the drag and for example not being able to start another drag. (cherry picked from commit b1d0928c8e3464e5a1a519263c5af0ea37782f76) M +5 -0 src/xwl/datasource.h M +7 -1 src/xwl/drag_x.cpp https://invent.kde.org/plasma/kwin/commit/2d88ce5a5d156581ec9290823eb39bb8a47689a1 *** Bug 446891 has been marked as a duplicate of this bug. *** |