After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770185 - Touchscreen: Impossible drag or close xwayland apps window touching the window title bar
Touchscreen: Impossible drag or close xwayland apps window touching the windo...
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: wayland
3.28.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
: 774947 786910 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-08-21 05:42 UTC by Strangiato
Modified: 2018-05-26 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Strangiato 2016-08-21 05:42:58 UTC
steps to reproduce
start Gnome on Wayland session from GDM login manager
open any gtk2 (gimp), qt4 (vlc player) or qt5 (qupzilla or smplayer) app
use touchscreen to drag or close the app window
nothing happens, touchscreen does no effect on window title bar

This problem does not happen with gtk3 apps running under Wayland.
Tested on Antergos (Arch-based).
Comment 1 Strangiato 2017-03-18 21:25:05 UTC
This problem is still present on 3.24 RC.
Comment 2 Stephen 2017-06-17 01:10:03 UTC
Identical behaviour still seen on 3.24.2

Weirdly enough it also seems to affect Firefox, despite that having been built with --enable-default-toolkit=cairo-gtk3

Is this on any dev's radar? It's been a problem for two releases now.
Comment 3 Stephen 2017-06-17 01:13:46 UTC
Strangely enough, I see the inverse behaviour with a pen (on a Surface Pro 3) - GIMP, SMPlayer, Firefox are all movable via the titlebar with the pen, whereas e.g. Files, Evolution, gedit are not.
Comment 4 Stephen 2017-06-17 01:18:54 UTC
Sorry for spamming this bug... when using the pen, the close button works in all cases, but for touch, the functionality of close matches that of drag.
Comment 5 Strangiato 2017-06-17 01:28:18 UTC
(In reply to Stephen from comment #2) 
> Weirdly enough it also seems to affect Firefox, despite that having been
> built with --enable-default-toolkit=cairo-gtk3
> 
Firefox gtk3 runs under xwayland.
Comment 6 David Greengas 2017-09-02 01:55:55 UTC
I can confirm this with Firefox. If I use a theme that has its own close button, it works just fine.
Comment 7 Strangiato 2017-09-20 03:27:58 UTC
Gnome 3.26 has the same problem.
Comment 8 Sebastien Bacher 2017-10-31 21:29:52 UTC
reported on Ubuntu as well, https://bugs.launchpad.net/gnome-shell/+bug/1728412
Comment 9 Jonas Ådahl 2017-11-02 04:31:02 UTC
*** Bug 786910 has been marked as a duplicate of this bug. ***
Comment 10 Jonas Ådahl 2017-11-02 04:31:22 UTC
*** Bug 774947 has been marked as a duplicate of this bug. ***
Comment 11 willovince 2017-11-18 23:29:18 UTC
Can confirm this for Shell 3.26.2 and mutter 3.26.2 on Arch Linux. I can't interact with the titlebar of XWayland apps via touchscreen.

After dismissing the onscreen keyboard I can't get it back by tapping on a text entry field.
Comment 12 Strangiato 2018-03-16 21:32:00 UTC
Gnome 3.28 has the same problem on Arch Linux.
Comment 13 Atri 2018-03-17 14:55:51 UTC
Not only on Arch; confirming it's also present on openSUSE Tumbleweed with Gnome 3.28
Comment 14 Stephen 2018-04-14 16:49:39 UTC
And with Fedora. This bug has now been around for four GNOME releases...

It's mystifying that lots of GNOME's design seems geared towards "touch friendliness", but a crippling touch bug has gone untouched for so long.

BTW pen control (CSD window dragging etc.) is now fine under GNOME Wayland.
Comment 15 Carlos Garnacho 2018-04-15 15:25:10 UTC
The last time I looked into this, it was a whole lot more troublesome. Events on the frame came from the GDK display connection, this brought 2 series of problems:

1) In X11 this is a second display connection, explicitly handling touch events there got in all sorts of weird interactions with the primary display connection, and the passive touch grab we set up there for touch gestures. This basically introduced a triple handling of the same events:
  a) From the passive grab
  b) The touch events as requested by XISelectEvents
  c) The XIPointerEmulated variant of the same touch events from b)

2) In wayland, this meant events still came from the only X11 connection we have, so the route of events was: 

  libinput->clutter->mutter->xwayland->gdk->mutter->frame


Fortunately, the large refactors needed to accomodate this neatly have happened over time, so it's gotten much saner to implement now. See https://gitlab.gnome.org/GNOME/mutter/merge_requests/78
Comment 16 Carlos Garnacho 2018-05-15 14:08:19 UTC
https://gitlab.gnome.org/GNOME/mutter/merge_requests/78 was merged to master earlier today. And I've just cherry picked to 3.28.
Comment 17 Atri 2018-05-23 01:07:01 UTC
Thanks for the patches; moving around windows and closing them now works.  However, moving maximised windows by grabbing them from the top-bar in gnome-shell still does not work. Works on Xorg though. As of commit 235c3518.
Comment 18 Carlos Garnacho 2018-05-23 08:12:20 UTC
Thanks for testing! Please file a gnome-shell issue for that, as the code allowing maximized window dragging from the top bar is there.
Comment 19 vst4rbot 2018-05-26 18:10:27 UTC
Almost 2 years since this was opened and still having this problem on both of my touchscreen thinkpads... Can't interact with the window bars at all on some applications. X220 Tablet and Yoga 20C0 both with Arch Linux, kernel 4.16.11-1-ARCH and GNOME 3.28.2-1.
Comment 20 Atri 2018-05-26 18:38:04 UTC
(In reply to Carlos Garnacho from comment #18)
> Thanks for testing! Please file a gnome-shell issue for that, as the code
> allowing maximized window dragging from the top bar is there.

I think it is this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/191

Although the bug references top-icon plus, basically, most things on the top bar don't respond to touch any more. Try caffeine, or the "Do not disturb button", etc.
Comment 21 Carlos Garnacho 2018-05-26 20:22:31 UTC
comment #17 actually is https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/112.

The bug(s) you reference are actually in those individual extensions, that they get touch handling "for free" on Xorg is just a byproduct. Those extensions ought to additionally handle CLUTTER_TOUCH_BEGIN/UPDATE/END.