Bug 651632 – [abrt] evolution-3.0.1-1.fc15: Process /usr/bin/evolution-settings was killed by signal 11 (SIGSEGV)

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 651632 - [abrt] evolution-3.0.1-1.fc15: Process /usr/bin/evolution-settings was killed by signal 11 (SIGSEGV)


Summary:	[abrt] evolution-3.0.1-1.fc15: Process /usr/bin/evolution-settings was killed...


Status:	RESOLVED OBSOLETE

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-06-01 12:13 UTC by Milan Crha
Modified:	2012-09-04 19:02 UTC

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

Description Milan Crha 2011-06-01 12:13:08 UTC

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

abrt version: 2.0.1
architecture:   x86_64
cmdline:        evolution-settings
component:      evolution
crash_function: mail_folder_cache_get_folder_from_uri
executable:     /usr/bin/evolution-settings
kernel:         2.6.38.6-27.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        evolution-3.0.1-1.fc15
rating:         4
reason:         Process /usr/bin/evolution-settings was killed by signal 11
(SIGSEGV)

+ Trace 227337

Thread 1 (Thread 0x7fc4989ba9a0 (LWP 31207))

#0 mail_folder_cache_get_folder_from_uri
at mail-folder-cache.c line 1292
#1 em_folder_tree_model_set_folder_info
at em-folder-tree-model.c line 706
#2 em_folder_tree_model_set_folder_info
at em-folder-tree-model.c line 654
#3 folder_tree_get_folder_info__done
at em-folder-tree.c line 325
#4 folder_tree_get_folder_info__done
at em-folder-tree.c line 224
#5 mail_msg_idle_cb
at mail-mt.c line 388
#6 g_main_dispatch
at gmain.c line 2440
#7 g_main_context_dispatch
at gmain.c line 3013
#8 g_main_context_iterate
at gmain.c line 3091
#9 g_main_loop_run
at gmain.c line 3299
#10 gtk_dialog_run
at gtkdialog.c line 1105
#11 folder_selection_button_clicked
at em-folder-selection-button.c line 263
#12 g_closure_invoke
at gclosure.c line 767
#13 signal_emit_unlocked_R
at gsignal.c line 3182
#14 g_signal_emit_valist
at gsignal.c line 2983
#15 g_signal_emit
at gsignal.c line 3040
#16 gtk_real_button_released
at gtkbutton.c line 1827
#17 g_closure_invoke
at gclosure.c line 767
#18 signal_emit_unlocked_R
at gsignal.c line 3182
#19 g_signal_emit_valist
at gsignal.c line 2983
#20 g_signal_emit
at gsignal.c line 3040
#21 gtk_button_button_release
at gtkbutton.c line 1719
#22 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 85
#23 g_closure_invoke
at gclosure.c line 767
#24 signal_emit_unlocked_R
at gsignal.c line 3290
#25 g_signal_emit_valist
at gsignal.c line 2993
#26 g_signal_emit
at gsignal.c line 3040
#27 gtk_widget_event_internal
at gtkwidget.c line 6114
#28 gtk_propagate_event
at gtkmain.c line 2597
#29 gtk_main_do_event
at gtkmain.c line 1872
#30 gdk_event_source_dispatch
at gdkeventsource.c line 318
#31 g_main_dispatch
at gmain.c line 2440
#32 g_main_context_dispatch
at gmain.c line 3013
#33 g_main_context_iterate
at gmain.c line 3091
#34 g_main_loop_run
at gmain.c line 3299
#35 gtk_main
at gtkmain.c line 1358
#36 main
at anjal-settings-main.c line 280

Comment 1 Milan Crha 2012-09-04 19:02:15 UTC

Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.