Titlebar of firefox does not respond to touch screen

[doniks]

I have a laptop with a touch screen and a new installation of 17.10.

For the most part the touch screen is supported ok. I can move around most windows ok, I can zoom in the pdf viewer with a two-finger-pinch gesture. However, firefox has a differently looking toolbar and I can neither move the window, nor does it react to tapping the minimise/maximise/close buttons.

I assume that I am running wayland by looking at these variables:

echo $WAYLAND_DISPLAY $XDG_SESSION_DESKTOP $XDG_SESSION_TYPE
wayland-0 ubuntu wayland
---
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: peter 10998 F...m pulseaudio
 /dev/snd/controlC0: peter 10998 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=f1546bcb-f4e8-4393-a32e-0f014e1e9bd3
InstallationDate: Installed on 2017-10-29 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: HP HP Pavilion x2 Detachable
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=e11fcd52-994f-4f5f-814f-f95ea37ccc46 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
Tags: artful wayland-session
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8181
dmi.board.vendor: HP
dmi.board.version: 42.25
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Pavilion x2 Detachable
dmi.sys.vendor: HP

[Strangiato Xanadu (strangiato)]

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).

[Strangiato Xanadu (strangiato)]

This problem is still present on 3.24 RC.

[Gnome-k (gnome-k)]

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.

[Gnome-k (gnome-k)]

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.

[Gnome-k (gnome-k)]

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.

[Strangiato Xanadu (strangiato)]

(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.

[dngreengas (dave-greengas)]

I can confirm this with Firefox. If I use a theme that has its own close button, it works just fine.

[Strangiato Xanadu (strangiato)]

Gnome 3.26 has the same problem.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1728412

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

apport information

[doniks (kaabud-lp)]

I can also reproduce it with thunderbird and kate.

Maybe something to do with the toolkit/ client-side-decorations?

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7

[doniks (kaabud-lp)]

@Joseph it happens in a new installation. I wouldn't expect this to be in the linux kernel, but if you are convinced that the test has value, please ping me again and I'll do the upstream kernel test

@Sebastien, while it does 'affect' firefox, I wonder whether the bug is actually somewhere else, like in gnome-something. As I said, I have the same in thunderbird and kate. I wouldn't be surprised if the list is longer. I just picked some other non-gnome applications

[Sebastien Bacher (seb128)]

the issue is likely in gnome-shell/xwayland dealing with legacy x11 softwares

[Sebastien Bacher (seb128)]

There is an upstream report about that on https://bugzilla.gnome.org/show_bug.cgi?id=786910

[Sebastien Bacher (seb128)]

other report https://bugzilla.gnome.org/show_bug.cgi?id=770185

[Sebastien Bacher (seb128)]

reported on Ubuntu as well, https://bugs.launchpad.net/gnome-shell/+bug/1728412

[Jonas Ådahl (jadahl)]

*** Bug 786910 has been marked as a duplicate of this bug. ***

[Jonas Ådahl (jadahl)]

*** Bug 774947 has been marked as a duplicate of this bug. ***

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[WilloVincent (willovince)]

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.

[Strangiato Xanadu (strangiato)]

Gnome 3.28 has the same problem on Arch Linux.

[Badshah400-s (badshah400-s)]

Not only on Arch; confirming it's also present on openSUSE Tumbleweed with Gnome 3.28

[Gnome-k (gnome-k)]

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.

[Carlos Garnacho (carlosg)]

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

[Carlos Garnacho (carlosg)]

https://gitlab.gnome.org/GNOME/mutter/merge_requests/78 was merged to master earlier today. And I've just cherry picked to 3.28.

[Badshah400-s (badshah400-s)]

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.

[Carlos Garnacho (carlosg)]

Thanks for testing! Please file a gnome-shell issue for that, as the code allowing maximized window dragging from the top bar is there.

[Vst4rbot (vst4rbot)]

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.

[Badshah400-s (badshah400-s)]

(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.

[Carlos Garnacho (carlosg)]

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.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[doniks (kaabud-lp)]

Still present in Ubuntu 18.04.1 LTS