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 774187 - touchscreen event under wayland causes any GTK3 app to crash
touchscreen event under wayland causes any GTK3 app to crash
Status: RESOLVED DUPLICATE of bug 776220
Product: mutter
Classification: Core
Component: wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-11-10 09:55 UTC by Pantelis Panayiotou
Modified: 2017-04-27 20:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
core dump (2.43 MB, application/gzip)
2016-11-10 09:55 UTC, Pantelis Panayiotou 		Details

Description Pantelis Panayiotou 2016-11-10 09:55:31 UTC 
Created attachment 339440 [details]
core dump

Hello Gnome developers, and thank you for your excellent work that has given us an amazing desktop.

This is an annoying bug that causes any GTK3 application to crash when using the touchscreen. Unless I'm mistaken, it hasn't been reported yet.

Steps to reproduce:

1. Start any GTK3 application, for instance:
$ gnome-calculator

2. Tap on the clock in the top panel, to open the calendar drop-down.

3. Now tap on the application's window.

4. The application crashes.

This is 100% reproducible on my machine. I'm running Arch Linux with Gnome 3.22 on a Dell Inspiron 15-7568.

Backtrace:

(gdb) bt

+ Trace 236846

  • #0 0x00007ffff6d6948d in
  • #1 ffi_call_unix64
  • #2 ffi_call
  • #3 0x00007ffff1f4708e in
  • #4 0x00007ffff1f43d20 in
  • #5 wl_display_dispatch_queue_pending
  • #6 0x00007ffff6d6f7e4 in
  • #7 gdk_display_get_event
  • #8 0x00007ffff6d6f4d2 in
  • #9 g_main_context_dispatch
  • #10 0x00007ffff5fbc7f0 in
  • #11 g_main_context_iteration
  • #12 g_application_run
  • #13 calculator_main
  • #14 __libc_start_main
  • #15 _start 






Comment 1


Pantelis Panayiotou





          2016-11-10 10:02:31 UTC
        



I forgot:

The crash does not happen when running the application using the X11 backend:
$ GDK_BACKEND=x11 gnome-calculator






Comment 2


Carlos Garnacho





          2016-11-10 10:42:50 UTC
        



Thanks for the bug report! This is a mutter issue, the event indicating the touch is down is not sent to the client underneath when leaving from a compositor grab (like the calendar's), so the next touch update event(s) are handled when the client is in an inconsistent state.

This is not legal according to the wayland protocol, so it's mutter which is acting wrong here.






Comment 3


Jan Alexander Steffens (heftig)





          2016-11-10 11:31:37 UTC
        



Hmm, can't GTK abort instead of segfault if it finds the state inconsistent?






Comment 4


Carlos Garnacho





          2016-11-10 12:23:38 UTC
        



Sure, we can add some asserts. Doesn't change the fact that the app will unexpectedly end :).






Comment 5


Volker Sobek (weld)





          2017-04-27 20:54:11 UTC
        



This is the same bug as 776220. I'm marking this here as duplicate because bug 776220 has a complete backtrace.

*** This bug has been marked as a duplicate of bug 776220 ***