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 636565 - [abrt] evolution-2.32.1-1.fc14: (SIGSEGV) propfind_msg, e2k_context_propfind, unmangle_sender_field
[abrt] evolution-2.32.1-1.fc14: (SIGSEGV) propfind_msg, e2k_context_propfind,...
Status: RESOLVED OBSOLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.32.x
Other Linux
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-12-06 07:55 UTC by Milan Crha
Modified: 2012-09-04 19:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2010-12-06 07:55:00 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=660103

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Crash occurred while sycing OWA Exchange account on startup.  After a
couple startups, Evo runs stably for a while.
component: evolution
crash_function: propfind_msg
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291560532
uid: 500

How to reproduce
-----
1. Start evolution (with OWA Exchange account)

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

+ Trace 224997

Thread 1 (Thread 20500)

  • #0 propfind_msg
    at e2k-context.c line 1676
  • #1 e2k_context_propfind
    at e2k-context.c line 1711
  • #2 unmangle_sender_field
    at camel-exchange-utils.c line 1812
  • #3 camel_exchange_utils_get_message
    at camel-exchange-utils.c line 2714
  • #4 exchange_folder_get_message_data
    at camel-exchange-folder.c line 151
  • #5 exchange_folder_get_message
    at camel-exchange-folder.c line 506
  • #6 camel_folder_get_message
    at camel-folder.c line 1752
  • #7 get_message_cb
    at camel-filter-driver.c line 1449
  • #8 camel_filter_search_get_message
    at camel-filter-search.c line 132
  • #9 junk_test
    at camel-filter-search.c line 674
  • #10 e_sexp_term_eval
    at e-sexp.c line 731
  • #11 e_sexp_eval
    at e-sexp.c line 1545
  • #12 camel_filter_search_match
  • #13 camel_filter_driver_filter_message
    at camel-filter-driver.c line 1548
  • #14 filter_filter
    at camel-folder.c line 202
  • #15 session_thread_proxy
    at camel-session.c line 321
  • #16 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #17 g_thread_create_proxy
    at gthread.c line 1897
  • #18 start_thread
    from /lib64/libpthread-2.12.90.so
  • #19 clone
    from /lib64/libc-2.12.90.so 






Comment 1


Milan Crha





          2011-04-14 05:17:15 UTC
        



Another downstream bug report from 2.32.2:
https://bugzilla.redhat.com/show_bug.cgi?id=696188

With steps:
1.  Opened evolution that was using the Exchange plugin.
2.  Sorted the messages by size.
3.  Deleted 3 messages of the largest size and evolution crashed.






Comment 2


Donald Edward Winslow





          2011-05-04 01:24:12 UTC
        



This is a common crash for me. This happens to me often when I try to sort messages into subfolders on the Exchange server.

I tried to report the bug at the Redhat Bugzilla linked above, and it redirected me here. I don't know what happened to the backtrace.






Comment 3


Milan Crha





          2011-05-11 16:08:29 UTC
        



Thanks for joining the bug. I didn't copy the backtrace, because it was too similar to the one which is above.

I tried some sorting by Size column in a folder with 717 messages on an exchange 2003 server to which I connect by evolution-exchange and it doesn't crash to me. I do something differently, probably. 

Could you try to run evolution under valgrind to see whether it'll hint us what is going wrong, please? You can run it like this:

   $ G_SLICE=always-malloc valgrind --num-callers=50  evolution &>log.txt

It'll be pretty slow, but maybe it'll discover something, and write it to the log.txt file, which I would like to ask you to attach here. Note that valgrind can avoid crash, sometimes.






Comment 4


Milan Crha





          2012-09-04 19:11:53 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.