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 735088 - gnome-shell crashed with SIGABRT in g_assertion_message()
gnome-shell crashed with SIGABRT in g_assertion_message()
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.12.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2014-08-20 09:51 UTC by Cristian Aravena Romero
Modified: 2021-07-05 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cristian Aravena Romero 2014-08-20 09:51:41 UTC
Open bug in launchpad.net:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1351011

"click on x to close the window > gnome-shell crash > looks like keyboard layout config is beeing ignored on gnome-shells automatic restart and english qwerty config is loaded automatically"

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at /build/buildd/glib2.0-2.41.1/./glib/gtestutils.c line 2306
  • #4 meta_window_unmanage
    at core/window.c line 1778
  • #5 event_callback
    at core/display.c line 2763
  • #6 filter_func
    at ui/ui.c line 261
  • #7 gdk_event_apply_filters
    at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventsource.c line 81
  • #8 gdk_event_source_translate_event
    at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventsource.c line 195
  • #9 _gdk_x11_display_queue_events
    at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventsource.c line 338
  • #10 gdk_display_get_event
    at /build/buildd/gtk+3.0-3.12.2/./gdk/gdkdisplay.c line 320
  • #11 gdk_event_source_dispatch
    at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventsource.c line 360
  • #12 g_main_dispatch
    at /build/buildd/glib2.0-2.41.1/./glib/gmain.c line 3064
  • #13 g_main_context_dispatch
    at /build/buildd/glib2.0-2.41.1/./glib/gmain.c line 3663
  • #14 g_main_context_iterate
    at /build/buildd/glib2.0-2.41.1/./glib/gmain.c line 3734
  • #15 g_main_loop_run
    at /build/buildd/glib2.0-2.41.1/./glib/gmain.c line 3928
  • #16 meta_run
    at core/main.c line 566
  • #17 main
    at main.c line 437

Comment 1 André Klapper 2015-01-03 22:04:05 UTC
Looks like mutter territory.
Is there a full stacktrace available of all threads, and not just one?
Comment 2 GNOME Infrastructure Team 2021-07-05 13:52:31 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.