Bug 666487 – Crash on send/receive cancellation

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 666487 - Crash on send/receive cancellation


Summary:	Crash on send/receive cancellation


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	3.2.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-12-19 09:02 UTC by Milan Crha
Modified:	2018-12-12 14:57 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Milan Crha 2011-12-19 09:02:13 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=768715

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
comment:        When i want to stop reception mail
crash_function: g_type_check_instance_cast
executable:     /usr/bin/evolution
kernel:         3.1.5-1.fc16.x86_64
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
reported_to:    file: Erreurs
time:           dim. 18 déc. 2011 09:44:32 CET

(The other threads are refreshing IMAPX accounts, see https://bugzilla.redhat.com/attachment.cgi?id=548358
for more info - it's too long backtrace.)

+ Trace 229296

Thread 1 (Thread 0x7fd7d8fad980 (LWP 3988))

#0 g_type_check_instance_cast
at gtype.c line 3985
#1 cancel_send_info
at mail-send-recv.c line 231
#2 g_hash_table_foreach
at ghash.c line 1420
#3 dialog_response
at mail-send-recv.c line 268
#4 g_closure_invoke
at gclosure.c line 774
#5 signal_emit_unlocked_R
at gsignal.c line 3272
#6 g_signal_emit_valist
at gsignal.c line 3003
#7 g_signal_emit
at gsignal.c line 3060
#8 g_closure_invoke
at gclosure.c line 774
#9 signal_emit_unlocked_R
at gsignal.c line 3272
#10 g_signal_emit_valist
at gsignal.c line 3003
#11 g_signal_emit
at gsignal.c line 3060
#12 ??
from /usr/lib64/libgtk-3.so.0
#13 g_closure_invoke
at gclosure.c line 774
#14 signal_emit_unlocked_R
at gsignal.c line 3202
#15 g_signal_emit_valist
at gsignal.c line 3003
#16 g_signal_emit
at gsignal.c line 3060
#17 ??
from /usr/lib64/libgtk-3.so.0
#18 ??
from /usr/lib64/libgtk-3.so.0
#19 g_closure_invoke
at gclosure.c line 774
#20 signal_emit_unlocked_R
at gsignal.c line 3310
#21 g_signal_emit_valist
at gsignal.c line 3013
#22 g_signal_emit
at gsignal.c line 3060
#23 ??
from /usr/lib64/libgtk-3.so.0
#24 gtk_propagate_event
from /usr/lib64/libgtk-3.so.0
#25 gtk_main_do_event
from /usr/lib64/libgtk-3.so.0
#26 ??
from /usr/lib64/libgdk-3.so.0
#27 g_main_dispatch
at gmain.c line 2425
#28 g_main_context_dispatch
at gmain.c line 2995
#29 g_main_context_iterate
at gmain.c line 3073
#30 g_main_loop_run
at gmain.c line 3281
#31 gtk_main
from /usr/lib64/libgtk-3.so.0
#32 main
at main.c line 696

Comment 1 Milan Crha 2018-12-12 14:57:30 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.