GNOME Bugzilla – Bug 774947
window title bars of Xwayland clients don't respond to touch events
Last modified: 2018-04-15 20:11:42 UTC
Greetings, and thank you all for your good work that has provided us with such a fine desktop.
I hope this is the correct place to report this issue.
Window title bars of Xwayland clients do not seem to respond to touch events (while title bars of native Wayland clients do). For instance, I can use my finger to drag gnome-terminal around the screen, and I can tap on the (x) button to close it. But when I try to do the same to Firefox or GIMP windows (both GTK2 apps that use Xwayland), nothing happens.
I reported this problem on Arch Linux Forums, and it looks like at least one more person is having the same problem:
Also, it looks like this is a Wayland-specific issue. All title bars handle touch events just fine under X11.
I'm using Gnome 3.22 with Wayland 1.12.0 on a Dell Inspiron 15 7000 series with touchscreen. More information about my system can be found in the aforementioned forum post.
I confirm this exists on Fedora 25 (Gnome 3.22) with Wayland. I am using a Lenovo Yoga 900 touchscreen laptop. To reproduce, start a gnome wayland session and open firefox and try to move the window using the title bar. On my machine, the title bar does not respond to touch events. You can still move the firefox window by dragging and empty part of the tab bar just below the title bar, as long as the window isn't maximized. If it is maximized, I haven't found a way to unmaximize it with touch (the mouse/touchpad works perfectly), and the close button doesn't respond. Native Wayland apps (Terminal, nautilus) don't have this issue in my hands. Please let me know if there is any other information I can provide!
I can confirm this bug on my laptop Lenovo G400S Touch running Arch. It happens only on Wayland session.
Probable duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=770185
(In reply to Stephen from comment #3)
> Probable duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=770185
*** This bug has been marked as a duplicate of bug 770185 ***