GNOME Bugzilla – Bug 301396
evolution exchange does not work for 2.2.1
Last modified: 2006-03-22 21:36:50 UTC
Distribution/Version: Ubuntu 5.04 I have tried numerous times to get the exchange plugin to work on evolution 2.2.1 and it just keeps coming up with error message that the evolution-exchange storage has crashed. It also messes up my calender alarms that I have locally. I using gnome 2.10 on ubuntu. This has worked fine on evolution 2.0.x and gnome 2.8 but seems broken after I have upgraded.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
okay - here is the output from bugbuddy - this is probably a duplicate but I just wanted to make sure it got reported because I could find anything about the plugin by searching for it. So sorry if it is a duplicate. From: <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.10.0 Subject: evolution crashes whenever I have the exchange plugin installed Distribution: Debian 3.1 Package: Evolution-Data-Server Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Ubuntu Synopsis: evolution crashes whenever I have the exchange plugin installed Bugzilla-Product: Evolution-Data-Server Bugzilla-Component: Calendar Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: evolution crashes whenever I have the exchange plugin installed and either unconfigured or configured Steps to reproduce the crash: 1. Install evolution plugin 2. Open exchange 3. receive crash Expected Results: should open without errors How often does this happen? everytime I open evolution 2.2.1 Additional Information: when I have the exchange plugin installed it also messes up my alerts and they crash also and do not alert me anymore so this makes me have to uninstall the plugin. Debugging Information: Backtrace was generated from '/usr/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229516672 (LWP 18461)] [New Thread -1264714832 (LWP 18486)] [New Thread -1281500240 (LWP 18485)] [New Thread -1231070288 (LWP 18462)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 58498
Thread 4 (Thread -1231070288 (LWP 18462))
Appears to be a unique stack trace, according to the simple-dup-finder.
I am kind of new to this - so what does that mean - do you need me to do anything?
That means that it doesn't appear to be a duplicate, so it's a new bug for the maintainers to look at. At this point, just sit back and wait for someone else to comment; this may be enough information for the maintainers to fix this issue, or they may decide to ask you for additional information. :)
This is a exchange connector bug, hence changing product to 'Connector'. This bug has been fixed in gnome head. Taking evolution build from head will resolve reporter's issue. Hence clsoing this bug as bug related to this has been raised and fixed. If reporter faces the same issue after getting latest build of evolution from gnome head, he can reopen this bug
*** Bug 305594 has been marked as a duplicate of this bug. ***
*** Bug 305351 has been marked as a duplicate of this bug. ***
*** Bug 304483 has been marked as a duplicate of this bug. ***
*** Bug 335519 has been marked as a duplicate of this bug. ***