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 707193 - evolution crashed with SIGSEGV in g_type_check_instance_is_a()
evolution crashed with SIGSEGV in g_type_check_instance_is_a()
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-08-31 18:57 UTC by Fabio Durán Verdugo
Modified: 2015-04-29 08:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Fabio Durán Verdugo 2013-08-31 18:57:03 UTC 
Open Evolution.
Disconnect a wireless network when evo scan the inbox.
evo show a message "*Evo offline*"
connect a wireless network.
crash.


https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1219274


Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 232440

Thread 1 (Thread 0x7f927ab21a40 (LWP 2278))

  • #0 g_type_check_instance_is_a
    at /build/buildd/glib2.0-2.37.6/./gobject/gtype.c line 3975
  • #1 e_alert_response
    at e-alert.c line 944
  • #2 _g_closure_invoke_va
    at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c line 840
  • #3 g_signal_emit_valist
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3234
  • #4 g_signal_emit
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3382
  • #5 gtk_real_button_released
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkbutton.c line 2101
  • #6 g_closure_invoke
    at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c line 777
  • #7 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3512
  • #8 g_signal_emit_valist
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3326
  • #9 g_signal_emit
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3382
  • #10 gtk_button_button_release
  • #11 _gtk_marshal_BOOLEAN__BOXEDv
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkmarshalers.c line 130
  • #12 _g_closure_invoke_va
    at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c line 840
  • #13 g_signal_emit_valist
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3234
  • #14 g_signal_emit
    at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c line 3382
  • #15 gtk_widget_event_internal
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkwidget.c line 7143
  • #16 gtk_widget_event
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkwidget.c line 6805
  • #17 propagate_event_up
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkmain.c line 2398
  • #18 propagate_event
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkmain.c line 2506
  • #19 gtk_main_do_event
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkmain.c line 1711
  • #20 gdk_event_source_dispatch
    at /build/buildd/gtk+3.0-3.9.12/./gdk/x11/gdkeventsource.c line 364
  • #21 g_main_dispatch
    at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3065
  • #22 g_main_context_dispatch
    at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3641
  • #23 g_main_context_iterate
    at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3712
  • #24 g_main_loop_run
    at /build/buildd/glib2.0-2.37.6/./glib/gmain.c line 3906
  • #25 gtk_main
    at /build/buildd/gtk+3.0-3.9.12/./gtk/gtkmain.c line 1157
  • #26 main
    at main.c line 686 






Comment 1


Milan Crha





          2014-10-10 07:35:42 UTC
        



Similar downstream bug report from 3.10.4:
https://bugzilla.redhat.com/show_bug.cgi?id=1150613

I do not recall seeing anything similar with 3.12.x, but that might be also because it's not that wide spread yet, who knows.






Comment 2


Milan Crha





          2015-04-29 08:25:23 UTC
        



I tried to reproduce this with current git master (after the release of the development version 3.17.1), which is pretty much the same as the current stable 3.16.2, and there doesn't happen this crash when following the steps from the comment #0. I'm closing this, also because of no duplicate in the 3.12.x series.