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 652519 - [abrt] evolution-3.0.2-2.fc15: camel_stream_reset: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-3.0.2-2.fc15: camel_stream_reset: Process /usr/bin/evolution...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-14 05:29 UTC by Milan Crha
Modified: 2012-09-04 19:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-06-14 05:29:51 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=712937

abrt version: 2.0.1
architecture:   x86_64
cmdline:        evolution
comment:        I had just set up IMAP to connect to my Gmail account. I
received my first email and clicked the notification to get back to Evolution.
I was in Calendar view, so I clicked "Mail" and Evolution crashed.
component:      evolution
crash_function: camel_stream_reset
executable:     /usr/bin/evolution
kernel:         2.6.38.7-30.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        evolution-3.0.2-2.fc15
rating:         4
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Mon Jun 13 12:27:06 2011

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

Thread 6 (Thread 0x7fe9e7f899a0 (LWP 3013))

  • #0 g_direct_hash
    at gutils.c line 3391
  • #1 g_hash_table_lookup_node
    at ghash.c line 313
  • #2 g_hash_table_lookup
    at ghash.c line 899
  • #3 handler_list_lookup
    at gsignal.c line 406
  • #4 signal_emit_unlocked_R
    at gsignal.c line 3169
  • #5 g_signal_emit_valist
    at gsignal.c line 2993
  • #6 g_signal_emit
    at gsignal.c line 3040
  • #7 gtk_widget_event_internal
    at gtkwidget.c line 6017
  • #8 gtk_propagate_event
    at gtkmain.c line 2597
  • #9 gtk_main_do_event
    at gtkmain.c line 1872
  • #10 gdk_event_source_dispatch
    at gdkeventsource.c line 318
  • #11 g_main_dispatch
    at gmain.c line 2441
  • #12 g_main_context_dispatch
    at gmain.c line 3014
  • #13 g_main_context_iterate
    at gmain.c line 3092
  • #14 g_main_loop_run
    at gmain.c line 3300
  • #15 gtk_main
    at gtkmain.c line 1358
  • #16 main
    at main.c line 734

Comment 1 Milan Crha 2012-09-04 19:02:19 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.