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 762553 - [abrt] Crash under alert_bar_response_cb()
[abrt] Crash under alert_bar_response_cb()
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Composer
3.18.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Tomas Popela
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-02-23 17:28 UTC by Milan Crha
Modified: 2018-12-12 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2016-02-23 17:28:48 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1302456

Version-Release number of selected component:
evolution-3.18.3-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        evolution
crash_function: _gtk_widget_get_toplevel
executable:     /usr/bin/evolution

I sent an email to a gmail address, but sending failed. Evolution displayed a dialog with a message from Google that I had exceeded the message size limit. I left that dialog open without pressing anything, then some time later, Evolution crashed.

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

Thread 1 (Thread 0x7fef2e5a9ac0 (LWP 26246))

  • #0 _gtk_widget_get_toplevel
    at gtkwidgetprivate.h line 364
  • #1 gtk_widget_hide
    at gtkwidget.c line 4808
  • #2 alert_bar_response_cb
    at e-alert-bar.c line 215
  • #3 g_cclosure_marshal_VOID__ENUMv
    at gmarshal.c line 1496
  • #4 _g_closure_invoke_va
    at gclosure.c line 864
  • #5 g_signal_emit_valist
    at gsignal.c line 3292
  • #6 g_signal_emit
    at gsignal.c line 3439
  • #7 alert_timeout_cb
    at e-alert.c line 444
  • #8 g_timeout_dispatch
    at gmain.c line 4577
  • #9 g_main_dispatch
    at gmain.c line 3154
  • #10 g_main_context_dispatch
    at gmain.c line 3769
  • #11 g_main_context_iterate
    at gmain.c line 3840
  • #12 g_main_loop_run
    at gmain.c line 4034
  • #13 gtk_dialog_run
    at gtkdialog.c line 1395
  • #14 e_alert_run_dialog
    at e-alert-dialog.c line 361
  • #15 e_alert_run_dialog_for_args
    at e-alert-dialog.c line 388
  • #16 composer_send_completed
    at em-composer-utils.c line 637
  • #17 g_simple_async_result_complete
    at gsimpleasyncresult.c line 801
  • #18 complete_in_idle_cb_for_thread
    at gsimpleasyncresult.c line 872
  • #19 g_main_dispatch
    at gmain.c line 3154
  • #20 g_main_context_dispatch
    at gmain.c line 3769
  • #21 g_main_context_iterate
    at gmain.c line 3840
  • #22 g_main_loop_run
    at gmain.c line 4034
  • #23 gtk_main
    at gtkmain.c line 1241
  • #24 main
    at main.c line 654

Comment 1 Milan Crha 2018-12-12 15:15:08 UTC
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.