[Bug 1788483] Re: 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()

Closing the gnome-shell part of this bug since the mutter fix is in cosmic now. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1788483] Re: 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()

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

[Bug 1788483] Re: 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()

Tracking in: https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16 ** Description changed: + https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16 https://gitlab.gnome.org/GNOME/mutter/issues/294 --- Crash happened when I tried to use Wacom

[Bug 1788483] Re: 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()

(Still waiting on sponsorship, but apparently “In Progress” is the right status for that.) ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1788483] Re: 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()

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

[Bug 1788483] Re: 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()

(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?) ** Patch added: "debdiff adding upstream patch, rebased"

[Bug 1788483] Re: 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()

** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Anders Kaseorg (andersk) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1788483] Re: 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()

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"

[Bug 1788483] Re: 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()

** Patch added: "debdiff adding upstream patch" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1788483] Re: 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()

Although the stack trace in this bug sounds a bit broken. I think bug 1790992 might be more accurate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1788483 Title: gnome-shell

[Bug 1788483] Re: 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()

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 ** No longer affects: gtk+3.0 (Ubuntu) ** Description changed: + https://gitlab.gnome.org/GNOME/mutter/issues/294 + + ---

[Bug 1788483] Re: 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()

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. ** Summary changed: - gnome-shell crashed with SIGABRT in g_assertion_message() + gnome-shell crashed with SIGABRT in