Summary: | kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Kevin Kofler <kevin.kofler> |
Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | fedorabugreporter88, kde.jfnff, nate, vlad.zahorodnii, xaver.hugl |
Priority: | NOR | Keywords: | wayland |
Version: | 5.25.3 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
URL: | https://gitlab.gnome.org/GNOME/gtk/-/issues/3737 | ||
Latest Commit: | https://invent.kde.org/plasma/kwin/commit/dccb6f6472ce9dcad259f0b3852896792dfb73b2 | Version Fixed In: | 5.25.5 |
Sentry Crash Report: |
Description
Kevin Kofler
2022-04-25 01:04:51 UTC
Ping? (3 more weeks have passed…) Is there anything more you need from me? (I have already posted GTK Wayland debugging logs that show that the KWin compositor is delivering the events to the wrong surface, see the linked https://gitlab.gnome.org/GNOME/gtk/-/issues/3737#note_1385359 . So, is there more that I can do to help getting this fixed?) Im having the same issue on Fedora 36 KDE 5.25.1 I had the issue on 5.24 as well. When using a touch screen when I try to press a popup menu on a gtk app it interacts with whatever is under the popup window. I dont know if you guys are still doing 15 minute bugs but this even effects firefox's hamburger menu meaning if youre a touch screen user it pops up immediately. Well, yes, I am not surprised that this can also be reproduced with a desktop/notebook/tablet with a touch device. At least, if you are using Plasma Desktop on Fedora KDE, you have the option to switch to an X11 session (pick "Plasma (X11)" instead of "Plasma (Wayland)" in SDDM) to work around this issue. (I am running Plasma Desktop on X11 on Fedora all the time.) That is not really an option on Plasma Mobile. As of 5.25.3 and KDE Frameworks 5.96, this bug still exists. I would be happy to help out in any way that I can. A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/2700 Git commit 94ee33e9be132175587a65d02934ed1bbfc96015 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 29/07/2022 at 11:39. Pushed by apol into branch 'master'. wayland: Fix touch event delivery to subsurfaces Use SurfaceInterface::inputSurfaceAt when deciding which surface are we entering when sending a pointer event from a touch, in case it falls onto a subsurface. M +18 -7 src/wayland/seat_interface.cpp M +4 -7 src/wayland/touch_interface.cpp M +1 -2 src/wayland/touch_interface.h https://invent.kde.org/plasma/kwin/commit/94ee33e9be132175587a65d02934ed1bbfc96015 Can this bugfix be backported to the upcoming 5.25.4 bugfix release? 5.25.4 is scheduled for August 4, so there are 5 days left to backport this. IMHO, this is a critical bugfix and definitely ought to be backported. It doesn't backport cleanly, so someone smarter than me would have to do it, and make the case that it's safe enough. Can you comment in https://invent.kde.org/plasma/kwin/-/merge_requests/2700? Git commit dccb6f6472ce9dcad259f0b3852896792dfb73b2 by Kevin Kofler, on behalf of Aleix Pol. Committed on 04/08/2022 at 21:41. Pushed by kkofler into branch 'Plasma/5.25'. wayland: Fix touch event delivery to subsurfaces Use SurfaceInterface::inputSurfaceAt when deciding which surface are we entering when sending a pointer event from a touch, in case it falls onto a subsurface. M +18 -7 src/wayland/seat_interface.cpp M +4 -7 src/wayland/touch_interface.cpp M +1 -2 src/wayland/touch_interface.h https://invent.kde.org/plasma/kwin/commit/dccb6f6472ce9dcad259f0b3852896792dfb73b2 |