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 523145 - evolution-exchange-storage crashed with SIGSEGV in icalvalue_set_parent()
evolution-exchange-storage crashed with SIGSEGV in icalvalue_set_parent()
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.32.x
Other Linux
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
: 525405 532754 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-18 12:04 UTC by Pedro Villavicencio
Modified: 2013-07-23 14:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2008-03-18 12:04:44 UTC 
This bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution-exchange/+bug/203242

"Just started up evolution. Just as it appeared to be finished reading the new messages, it crashed. I hadn't clicked or typed anything."

".

+ Trace 192765

Thread 1 (process 30028)

  • #0 icalvalue_set_parent
    at icalvalue.c line 1383
  • #1 icalproperty_free
    at icalproperty.c line 233
  • #2 icalcomponent_free
    at icalcomponent.c line 240
  • #3 mail_util_demangle_meeting_related_message
    at mail-utils.c line 445
  • #4 get_message
    at mail-stub-exchange.c line 2367
  • #5 connection_handler
    at mail-stub.c line 271
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 bonobo_main
    at bonobo-main.c line 311
  • #10 main
    at main.c line 238
  • #11 __libc_start_main
    from /lib/libc.so.6
  • #12 _start 






Comment 1


Johnny Jacob





          2008-07-23 02:23:19 UTC
        



*** Bug 532754 has been marked as a duplicate of this bug. ***






Comment 2


Johnny Jacob





          2008-07-23 02:25:12 UTC
        



*** Bug 525405 has been marked as a duplicate of this bug. ***






Comment 3


Milan Crha





          2011-03-18 06:49:48 UTC
        



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





+
Trace
    226366






Thread 1
          (Thread 0x7f232b7fe700 (LWP 3072))


    

  • 
#0
pvl_remove

    
                at pvl.c
                  line
                  393

    

    • 

  • 
#1
icalcomponent_free

    
                at icalcomponent.c
                  line
                  259

    

    • 

  • 
#2
icalcomponent_free

    
                at icalcomponent.c
                  line
                  271

    

    • 

  • 
#3
icalcomponent_free

    
                at icalcomponent.c
                  line
                  271

    

    • 

  • 
#4
mail_util_demangle_meeting_related_message

    
                at mail-utils.c
                  line
                  442

    

    • 

  • 
#5
unmangle_sender_field

    
                at camel-exchange-utils.c
                  line
                  1872

    

    • 

  • 
#6
camel_exchange_utils_get_message

    
                at camel-exchange-utils.c
                  line
                  2721

    

    • 

  • 
#7
exchange_folder_get_message_data

    
                at camel-exchange-folder.c
                  line
                  151

    

    • 

  • 
#8
exchange_folder_get_message

    
                at camel-exchange-folder.c
                  line
                  509

    

    • 

  • 
#9
camel_folder_get_message

    
                at camel-folder.c
                  line
                  1752

    

    • 

  • 
#10
get_message_exec

    
                at mail-ops.c
                  line
                  1905

    

    • 

  • 
#11
mail_msg_proxy

    
                at mail-mt.c
                  line
                  469

    

    • 

  • 
#12
g_thread_pool_thread_proxy

    
                at gthreadpool.c
                  line
                  319

    

    • 

  • 
#13
g_thread_create_proxy

    
                at gthread.c
                  line
                  1897

    

    • 

  • 
#14
start_thread

    
                at pthread_create.c
                  line
                  301

    

    • 

  • 
#15
clone

    
                at ../sysdeps/unix/sysv/linux/x86_64/clone.S
                  line
                  115

    

    • 













Comment 4


André Klapper





          2012-09-20 14:49:47 UTC
        



The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers.

If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible).

There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX.
Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".






Comment 5


André Klapper





          2013-07-23 14:29:52 UTC
        



evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago.

evolution-exchange is now deprecated and not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.

Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported.
Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.