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 790937 - gnome-shell crashed with signal 5 in g_log_default_handler()
gnome-shell crashed with signal 5 in g_log_default_handler()
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: wayland
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
: 792163 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-11-28 12:38 UTC by Cristian Aravena Romero
Modified: 2021-07-05 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cristian Aravena Romero 2017-11-28 12:38:54 UTC 
Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732878

"gnome-shell crashed with signal 5 in g_log_default_handler()"



BackTrace:

+ Trace 238197

  • #0 raise
    at ../sysdeps/unix/sysv/linux/raise.c line 51
  • #1 dump_gjs_stack_on_signal_handler
    at ../src/main.c line 372
  • #2 <signal handler called>
  • #3 _g_log_abort
    at ../../../../glib/gmessages.c line 554
  • #4 g_log_default_handler
    at ../../../../glib/gmessages.c line 3051
  • #5 default_log_handler
    at ../src/main.c line 315
  • #6 g_logv
    at ../../../../glib/gmessages.c line 1341
  • #7 g_log
    at ../../../../glib/gmessages.c line 1403
  • #8 x_io_error
    at wayland/meta-xwayland.c line 418
  • #9 _XIOError
    at ../../src/XlibInt.c line 1469
  • #10 _XEventsQueued
    at ../../src/xcb_io.c line 352
  • #11 XPending
    at ../../src/Pending.c line 55
  • #12 gdk_check_xpending
    at ../../../../../gdk/x11/gdkeventsource.c line 269
  • #13 gdk_event_source_prepare
    at ../../../../../gdk/x11/gdkeventsource.c line 287
  • #14 g_main_context_prepare
    at ../../../../glib/gmain.c line 3450
  • #15 g_main_context_iterate
    at ../../../../glib/gmain.c line 3866
  • #16 g_main_loop_run
    at ../../../../glib/gmain.c line 4082
  • #17 meta_run
    at core/main.c line 648
  • #18 main
    at ../src/main.c line 530 

Regards,
--
Cristian
Comment 1 Florian Müllner 2017-11-28 14:59:38 UTC 
> format=format@entry=0x7f3c825d1af0 "Connection to xwayland lost"

XWayland went away, which currently is a fatal error for mutter. What exactly is going on will need further investigation, as the stacktrace only handles the mutter/gnome-shell side - whether we sent incorrect input that XWayland cannot handle, or whether the crash is a genuine bug in XWayland ideally needs the XWayland backtrace, or at least the relevant journal log.

This is possibly NOTGNOME (as XWayland is a freedesktop project), but for now let's move this to mutter for further investigation.
Comment 2 André Klapper 2018-01-03 20:04:07 UTC 
*** Bug 792163 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2018-01-03 20:06:48 UTC 
*** Bug 792163 has been marked as a duplicate of this bug. ***
Comment 4 GNOME Infrastructure Team 2021-07-05 13:52:55 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.