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 635161 - [abrt] evolution-2.32.0-2.fc14: (SIGSEGV) content_info_to_db, g_string_new
[abrt] evolution-2.32.0-2.fc14: (SIGSEGV) content_info_to_db, g_string_new
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-11-18 10:01 UTC by Milan Crha
Modified: 2012-09-04 19:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2010-11-18 10:01:22 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=654125

abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289945650
uid: 500

How to reproduce
-----
1. I logged-in to gmail.
2. Open terminal, then login as root using su command.
3. Suddenly, I saw a pop-up at the top of screen saying this package crashed.

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

Thread 1 (Thread 32322)

  • #0 magazine_chain_pop_head
    at gslice.c line 492
  • #1 thread_memory_magazine1_alloc
    at gslice.c line 795
  • #2 g_slice_alloc
    at gslice.c line 833
  • #3 g_string_sized_new
    at gstring.c line 415
  • #4 g_string_new
    at gstring.c line 441
  • #5 content_info_to_db
    at camel-folder-summary.c line 540
  • #6 content_info_to_db
    at camel-imap-summary.c line 377
  • #7 perform_content_info_save_to_db
    at camel-folder-summary.c line 2090
  • #8 save_to_db_cb
    at camel-folder-summary.c line 2135
  • #9 g_hash_table_foreach
    at ghash.c line 1328
  • #10 save_message_infos_to_db
    at camel-folder-summary.c line 2195
  • #11 camel_folder_summary_save_to_db
    at camel-folder-summary.c line 2254
  • #12 imap_sync_offline
    at camel-imap-folder.c line 1438
  • #13 imap_sync
    at camel-imap-folder.c line 1710
  • #14 camel_folder_sync
    at camel-folder.c line 1124
  • #15 vee_folder_sync
    at camel-vee-folder.c line 1037
  • #16 camel_folder_sync
    at camel-folder.c line 1124
  • #17 refresh_folders_exec
    at mail-send-recv.c line 911
  • #18 mail_msg_proxy
    at mail-mt.c line 469
  • #19 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #20 g_thread_create_proxy
    at gthread.c line 1897
  • #21 start_thread
    at pthread_create.c line 301
  • #22 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133

Comment 1 Milan Crha 2011-10-06 17:33:16 UTC
Another similar downstream bug report from 3.0.3:
https://bugzilla.redhat.com/show_bug.cgi?id=743138

Thread 1 (Thread 0xaaefeb70 (LWP 4185))

  • #0 __kernel_vsyscall
    at arch/x86/vdso/vdso32/sysenter.S line 49
  • #1 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 __GI_abort
    at abort.c line 93
  • #3 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 198
  • #4 malloc_printerr
    at malloc.c line 6283
  • #5 __GI___vasprintf_chk
    at vasprintf_chk.c line 86
  • #6 vasprintf
    at /usr/include/bits/stdio2.h line 199
  • #7 g_vasprintf
    at gprintf.c line 318
  • #8 g_string_append_vprintf
    at gstring.c line 1422
  • #9 g_string_append_printf
    at gstring.c line 1526
  • #10 content_info_to_db
    at camel-folder-summary.c line 545
  • #11 content_info_to_db
    at camel-imapx-summary.c line 425
  • #12 perform_content_info_save_to_db
    at camel-folder-summary.c line 2072
  • #13 save_to_db_cb
    at camel-folder-summary.c line 2117
  • #14 g_hash_table_foreach
    at ghash.c line 1326
  • #15 save_message_infos_to_db
    at camel-folder-summary.c line 2179
  • #16 camel_folder_summary_save_to_db
    at camel-folder-summary.c line 2240
  • #17 camel_folder_summary_save_to_db
    at camel-folder-summary.c line 2208
  • #18 imapx_command_fetch_new_messages_done
    at camel-imapx-server.c line 3953
  • #19 imapx_completion
    at camel-imapx-server.c line 1959
  • #20 imapx_step
    at camel-imapx-server.c line 1985
  • #21 parse_contents
    at camel-imapx-server.c line 4816
  • #22 imapx_parser_thread
    at camel-imapx-server.c line 4883
  • #23 g_thread_create_proxy
    at gthread.c line 1955
  • #24 start_thread
    at pthread_create.c line 305
  • #25 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133

Comment 2 Milan Crha 2012-09-04 19:05:44 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.