Launchpad has imported 22 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=770185.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2016-08-21T05:42:58+00:00 Strangiato Xanadu wrote: 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). Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/0 ------------------------------------------------------------------------ On 2017-03-18T21:25:05+00:00 Strangiato Xanadu wrote: This problem is still present on 3.24 RC. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/1 ------------------------------------------------------------------------ On 2017-06-17T01:10:03+00:00 Gnome-k wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/2 ------------------------------------------------------------------------ On 2017-06-17T01:13:46+00:00 Gnome-k wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/3 ------------------------------------------------------------------------ On 2017-06-17T01:18:54+00:00 Gnome-k wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/4 ------------------------------------------------------------------------ On 2017-06-17T01:28:18+00:00 Strangiato Xanadu wrote: (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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/5 ------------------------------------------------------------------------ On 2017-09-02T01:55:55+00:00 dngreengas wrote: I can confirm this with Firefox. If I use a theme that has its own close button, it works just fine. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/6 ------------------------------------------------------------------------ On 2017-09-20T03:27:58+00:00 Strangiato Xanadu wrote: Gnome 3.26 has the same problem. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/7 ------------------------------------------------------------------------ On 2017-10-31T21:29:52+00:00 Sebastien Bacher wrote: reported on Ubuntu as well, https://bugs.launchpad.net/gnome- shell/+bug/1728412 Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/32 ------------------------------------------------------------------------ On 2017-11-02T04:31:02+00:00 Jonas Ådahl wrote: *** Bug 786910 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/33 ------------------------------------------------------------------------ On 2017-11-02T04:31:22+00:00 Jonas Ådahl wrote: *** Bug 774947 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/34 ------------------------------------------------------------------------ On 2017-11-18T23:29:18+00:00 WilloVincent wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/36 ------------------------------------------------------------------------ On 2018-03-16T21:32:00+00:00 Strangiato Xanadu wrote: Gnome 3.28 has the same problem on Arch Linux. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/37 ------------------------------------------------------------------------ On 2018-03-17T14:55:51+00:00 Badshah400-s wrote: Not only on Arch; confirming it's also present on openSUSE Tumbleweed with Gnome 3.28 Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/38 ------------------------------------------------------------------------ On 2018-04-14T16:49:39+00:00 Gnome-k wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/39 ------------------------------------------------------------------------ On 2018-04-15T15:25:10+00:00 Carlos Garnacho wrote: 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 Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/40 ------------------------------------------------------------------------ On 2018-05-15T14:08:19+00:00 Carlos Garnacho wrote: https://gitlab.gnome.org/GNOME/mutter/merge_requests/78 was merged to master earlier today. And I've just cherry picked to 3.28. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/41 ------------------------------------------------------------------------ On 2018-05-23T01:07:01+00:00 Badshah400-s wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/42 ------------------------------------------------------------------------ On 2018-05-23T08:12:20+00:00 Carlos Garnacho wrote: Thanks for testing! Please file a gnome-shell issue for that, as the code allowing maximized window dragging from the top bar is there. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/43 ------------------------------------------------------------------------ On 2018-05-26T18:10:27+00:00 Vst4rbot wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/44 ------------------------------------------------------------------------ On 2018-05-26T18:38:04+00:00 Badshah400-s wrote: (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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/45 ------------------------------------------------------------------------ On 2018-05-26T20:22:31+00:00 Carlos Garnacho wrote: 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. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/46 ** Changed in: mutter Status: Unknown => Fix Released ** Changed in: mutter Importance: Unknown => Medium ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #191 https://gitlab.gnome.org/GNOME/gnome-shell/issues/191 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1728412 Title: Titlebar of firefox does not respond to touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1728412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
