gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal() from meta_input_settings_x11_set_tablet_keep_aspect()

StacktraceTop:
 g_assertion_message (domain=0x7fc6589ef017 "Gdk", file=0x7fc658a0d7e0 "../../../../../gdk/x11/gdkdisplay-x11.c", line=2870, func=0x7fc658a0de80 <__func__.75276> "gdk_x11_display_error_trap_pop_internal", message=0x557136911ec0 "assertion failed: (trap->end_sequence == 0)") at ../../../../glib/gtestutils.c:2574
 g_assertion_message_expr () at ../../../../glib/gtestutils.c:2597
 gdk_x11_display_error_trap_pop_internal (display=<optimized out>, need_code=1) at ../../../../../gdk/x11/gdkdisplay-x11.c:2870
 meta_input_settings_x11_set_tablet_keep_aspect (settings=<optimized out>, device=0xffffffff, logical_monitor=0xffffffff, keep_aspect=806846624) at backends/x11/meta-input-settings-x11.c:836
 ?? ()

The bug is either in gtk+3.0 or in mutter. But since it's the gnome-shell process crashing we should also keep a task for that so that others can find the bug.

Fix committed to mutter, scheduled for release in version 3.30.1

https://gitlab.gnome.org/GNOME/mutter/commit/a3d9f987c830
https://gitlab.gnome.org/GNOME/mutter/issues/294

Although the stack trace in this bug sounds a bit broken. I think bug 1790992 might be more accurate.

The attachment "debdiff adding upstream patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

(Is it really correct to mark this as “In Progress” and assigned to me when there’s nothing else I can do to move this forward except wait for a sponsor to pay attention?)

Yes, because there is no "blocked" status. "In Progress" includes waiting for reviews when nothing is really happening. This is normal.

It should be assigned so as to show that someone has done or will do the work. It's often too hard (or too much effort) to find that information in the comments section alone. If a bug is left unassigned it may then get assigned to a second person, unknowing that a first has already done the work.

(Still waiting on sponsorship, but apparently “In Progress” is the right status for that.)

Tracking in:
https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16

This bug was fixed in the package mutter - 3.30.0-6

---------------
mutter (3.30.0-6) unstable; urgency=medium

  * Team upload

  [ Simon McVittie ]
  * Update to upstream git master branch at commit 3.30.0-28-g95649fd2b.
    According to upstream, all of this should be in 3.30.1.
    - In particular this fixes a crash when combining a touchscreen
      and graphics tablet (Closes: #910370, #908153, LP: #1788483)
  * d/libmutter-3-0.symbols:
    - Ignore removal of private function meta_input_device_is_trackball()
    - Add meta_region_scale_double()

  [ Jeremy Bicha ]
  * Modify debian/skip-failing-tests.patch:
    - Go back to skipping the actor-shader-effect-test since it's flaky
    (LP: #1795556)

 -- Simon McVittie <email address hidden> Mon, 08 Oct 2018 07:53:09 +0100

Closing the gnome-shell part of this bug since the mutter fix is in cosmic now.