Bug 1302456

Summary: [abrt] evolution: _gtk_widget_get_toplevel(): evolution killed by signal 11
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro+wrong-account-do-not-cc>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c2de125c815f8d181c0a80656bbc48c4957b1bee
Whiteboard: abrt_hash:d403d8c8d4b7f6ab267a3b0131ae90f0216c9da8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-23 17:28:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Michael Catanzaro 2016-01-27 23:23:33 UTC 
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
journald_cursor: s=f4e3d31c2cd74765bfef86f28866eb2f;i=2d262;b=64d65b1b533b4f11b1c3a8ef056702f8;m=63a22233e;t=52a58552e36cb;x=336277f8f5a9730b
kernel:         4.3.3-300.fc23.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _gtk_widget_get_toplevel at gtkwidgetprivate.h:364
 #1 gtk_widget_hide at gtkwidget.c:4808
 #2 alert_bar_response_cb at e-alert-bar.c:215
 #3 g_cclosure_marshal_VOID__ENUMv at gmarshal.c:1496
 #4 _g_closure_invoke_va at gclosure.c:864
 #7 alert_timeout_cb at e-alert.c:444
 #13 gtk_dialog_run at gtkdialog.c:1395
 #14 e_alert_run_dialog at e-alert-dialog.c:361
 #15 e_alert_run_dialog_for_args at e-alert-dialog.c:388
 #16 composer_send_completed at em-composer-utils.c:637
Comment 1 Michael Catanzaro 2016-01-27 23:23:39 UTC 
Created attachment 1118896 [details]
File: backtrace
Comment 2 Michael Catanzaro 2016-01-27 23:23:40 UTC 
Created attachment 1118897 [details]
File: cgroup
Comment 3 Michael Catanzaro 2016-01-27 23:23:42 UTC 
Created attachment 1118898 [details]
File: core_backtrace
Comment 4 Michael Catanzaro 2016-01-27 23:23:43 UTC 
Created attachment 1118899 [details]
File: dso_list
Comment 5 Michael Catanzaro 2016-01-27 23:23:44 UTC 
Created attachment 1118900 [details]
File: environ
Comment 6 Michael Catanzaro 2016-01-27 23:23:45 UTC 
Created attachment 1118901 [details]
File: exploitable
Comment 7 Michael Catanzaro 2016-01-27 23:23:45 UTC 
Created attachment 1118902 [details]
File: limits
Comment 8 Michael Catanzaro 2016-01-27 23:23:47 UTC 
Created attachment 1118903 [details]
File: maps
Comment 9 Michael Catanzaro 2016-01-27 23:23:48 UTC 
Created attachment 1118904 [details]
File: open_fds
Comment 10 Michael Catanzaro 2016-01-27 23:23:48 UTC 
Created attachment 1118905 [details]
File: proc_pid_status
Comment 11 Michael Catanzaro 2016-01-27 23:23:49 UTC 
Created attachment 1118906 [details]
File: var_log_messages
Comment 12 Milan Crha 2016-01-28 08:11:48 UTC 
Thanks for a bug report. If I read the backtrace properly, then the crash happened when some message finished sending (whether successfully or not I do not see from the backtrace). It also shows that the evolution had been showing some other prompt; again, I do not see from the backtrace what it was asking.

Do you recall what the evolution was doing right before the crash, please?
Comment 13 Michael Catanzaro 2016-01-28 17:59:33 UTC 
Sorry, I skipped through the ABRT dialog without adding details, and there wasn't any way to go back... then I meant to post here but forgot. Yes, I remember: 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.
Comment 14 Milan Crha 2016-02-23 17:28:05 UTC 
Okay, thanks. I moved this upstream [1]. Please see it for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=762553