GNOME Bugzilla – Bug 268762
Crash when opening Exchange mailbox
Last modified: 2006-01-02 06:18:29 UTC
Distribution: Debian testing/unstable Package: Evolution Priority: Normal Version: GNOME2.8.1 2.0.2 Gnome-Distributor: Ubuntu Synopsis: Crash when opening Exchange mailbox Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.0.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Retrieving email until about ~69% then crash occurs. This is my first time opening my mailbox with the Exchange connector. Steps to reproduce the crash: 1. Open Exchange Inbox 2. 3. Expected Results: Mail Retrieval How often does this happen? Consistently. It never works correctly. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.0' (no debugging symbols found)...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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1091720192 (LWP 30048)] [New Thread 1150348208 (LWP 30081)] [Thread debugging using libthread_db enabled] [New Thread 1091720192 (LWP 30048)] [New Thread 1150348208 (LWP 30081)] [Thread debugging using libthread_db enabled] [New Thread 1091720192 (LWP 30048)] [New Thread 1150348208 (LWP 30081)] (no debugging symbols found)...[New Thread 1141955504 (LWP 30079)] (no debugging symbols found)...[New Thread 1133169584 (LWP 30078)] (no debugging symbols found)...[New Thread 1124608944 (LWP 30061)] (no debugging symbols found)...[New Thread 1116203952 (LWP 30060)] (no debugging symbols found)...[New Thread 1107811248 (LWP 30059)] (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 __kernel_vsyscall ()
+ Trace 51312
Thread 3 (Thread 1141955504 (LWP 30079))
Unknown reporter: rob.caldwell@radian.biz, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** http://bugzilla.ximian.com/show_bug.cgi?id=69832 has been marked as a duplicate of this bug. ***
*** http://bugzilla.ximian.com/show_bug.cgi?id=69874 has been marked as a duplicate of this bug. ***
*** http://bugzilla.ximian.com/show_bug.cgi?id=69893 has been marked as a duplicate of this bug. ***
Not able to reproduce this on my setup here. Would have to run valgrind on it to see whats going wrong. Need some steps to reproduce this.
*** http://bugzilla.ximian.com/show_bug.cgi?id=69642 has been marked as a duplicate of this bug. ***
I have not been able to reproduce this on my setup here. It perhaps has got something to do with the data being fetched/processed. It would be great if we could get a valgrind output of evolution-exchange while we get this error. But, you would either need debug packages or build exchange so that we get the symbols in the output.
Is this crash still happening? Has anyone tried any newer versions of Evolution?
(In reply to comment #8) > Is this crash still happening? > Has anyone tried any newer versions of Evolution? > The Exchange Connector is working much better in Evolution 2.4.1. Evo does still occasionally crash (especially when I click the Send/Receive button), but I don't think it's the same issue.
I am closing this bug, For the crash when you press send/recv button, please file a bug witht the stack traces when it crashes.