Bug 657804 – Crash when checking new mails

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 657804 - Crash when checking new mails


Summary:	Crash when checking new mails


Status:	RESOLVED DUPLICATE of bug 651062

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	3.0.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-08-31 11:04 UTC by Lionel Landwerlin
Modified:	2011-09-08 11:40 UTC

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

Description Lionel Landwerlin 2011-08-31 11:04:13 UTC

On Debian Sid, Evolution 3.0.2, when clicking the Send/Receive button :

Program received signal SIGSEGV, Segmentation fault.

+ Trace 228284

Thread 140737353763200 (LWP 25188)

#0 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 3269
#1 g_signal_emit_valist
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 2983
#2 g_signal_emit
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 3040
#3 g_object_dispatch_properties_changed
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gobject.c line 925
#4 g_object_notify_queue_thaw
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gobjectnotifyqueue.c line 132
#5 g_object_notify_by_spec_internal
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gobject.c line 983
#6 g_object_notify
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gobject.c line 1024
#7 mail_msg_check_error
at mail-mt.c line 216
#8 mail_msg_idle_cb
at mail-mt.c line 389
#9 g_main_dispatch
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 2440
#10 g_main_context_dispatch
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3013
#11 g_main_context_iterate
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3091
#12 g_main_loop_run
at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3299
#13 gtk_main
at /build/buildd-gtk+3.0_3.0.12-1-amd64-KTvLTO/gtk+3.0-3.0.12/./gtk/gtkmain.c line 1358
#14 main
at main.c line 734

Comment 1 Milan Crha 2011-09-08 11:14:37 UTC

Thanks for a bug report. Can this be related to bug #651062, where was fixed a regression I caused in 3.0.2? The is included in the recently released 3.0.3, thus if you could retest with it then it'll be the best.

Comment 2 Lionel Landwerlin 2011-09-08 11:26:22 UTC

It might be, I'm running 3.0.3 now and haven't seen any crash so far.

Comment 3 Milan Crha 2011-09-08 11:40:59 UTC

Thanks for the update. I'm closing this as a duplicate of it then, but feel free to reopen if you face this with 3.0.3 or later version.

*** This bug has been marked as a duplicate of bug 651062 ***