GNOME Bugzilla – Bug 322901
evolution-exchange-storage-2.4 crash on startup/connect to server
Last modified: 2006-06-07 18:08:24 UTC
Distribution: Gentoo Base System version 1.12.0_pre11 Package: Connector Severity: major Version: GNOME2.12.1 2.4.x Gnome-Distributor: Gentoo Synopsis: evolution-exchange-storage-2.4 crash on startup/connect to server Bugzilla-Product: Connector Bugzilla-Component: Connector Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: evolution-exchange-storage-2.4 crashes on startup of evolution-2.4 Steps to reproduce the crash: 1. Start evolution-2.4 2. evolution starts evolution-exchange-storage-2.4 in background, which connects to an Exchange server 3. evolution-exchange-storage-2.4 crashes Expected Results: Should not crash ;-) How often does this happen? In 90% of all evolution startups where the Exchange server is reachable Additional Information: I'm not quite sure whether all instances of evolution-exchange-storage-2.4 crash. Sometimes I can browse my Exchange mail folders nevertheless, but the calendar function is dead. When I restart evolution 2-3 times I'm sometimes then, after the 3rd restart or so, able to browse the calendar, too. Debugging Information: Backtrace was generated from '/usr/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5259)] [New Thread 32769 (LWP 5260)] [New Thread 16386 (LWP 5261)] [New Thread 131076 (LWP 5525)] [New Thread 98310 (LWP 5329)] 0xb672f9eb in waitpid () from /lib/libpthread.so.0
+ Trace 64363
Thread 5 (Thread 98310 (LWP 5329))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-01 07:46 UTC -------
According to simple-dup-finder this is a unique stack trace.
Created attachment 55686 [details] Debugging information on evolution-exchange-storage crash I just upgraded to version 2.4.2 of evolution and evolution-exchange. At first glance, it worked fine, however, after a restart of evolution (maybe a dataserver was still running) it happened again. Debugging output is attached.
looks like libsoup issue. Poornima, is this same as libsoup issue connector was having?
Upgraded to evolution-2.4.2.1 and libsoup-2.2.7 today: looks quite like a "resolved" - the crash has not happened since. Regards, Birger
*** Bug 340628 has been marked as a duplicate of this bug. ***
Version of evolution running when crash observed with Fedora Core 5 is: evolution-connector-debuginfo-2.6.1-1.fc5.1 evolution-devel-2.6.1-1.fc5.2 evolution-data-server-debuginfo-1.6.1-1.fc5.2 evolution-debuginfo-2.6.1-1.fc5.2 evolution-data-server-devel-1.6.1-1.fc5.2 evolution-2.6.1-1.fc5.2 evolution-webcal-2.4.1-3.2 evolution-sharp-0.10.2-9 evolution-data-server-1.6.1-1.fc5.2 evolution-connector-2.6.1-1.fc5.1 If there's a libaoup patch for 2.6, I'd love to try it. :-D JAA
james, see comment #4, which is your libsoup version. Using the latest libsoup should help.
*** Bug 341083 has been marked as a duplicate of this bug. ***
# rpm -qa | grep libsoup libsoup-2.2.92-1.fc5.1 I am assuming that this is that latest libsoup.... is that a valid assumption? If so, I am still experiencing the problem. (This is in response to the question posed on bug 341083. See comment #8 above as well as comment #7)
I am currently running Core 5 with what I think is the latest libsoup version. rpm -aq | grep libsoup libsoup-2.2.92-1.fc5.1 Is this not the latest? If not, I'd love to update it :D Cheers JAA
*** Bug 342250 has been marked as a duplicate of this bug. ***
I don't know if this is valuable information or not. I am finding that if I keep restarting Evolution that it does eventually come up and stay up. Often it will take as many as 15 attempts but it will come up. Once it is up it is usually pretty stable.
argh, this was never "reassign to default owner of new component"ed, so I never saw the bug. Can someone get a stack trace with debug symbols? It's hard to figure out the problem without it...
There is a stack trace on bug 341083 which was closed as a duplicate of this. If you need I can generate another one.
*** Bug 336728 has been marked as a duplicate of this bug. ***
Woo! Hoo!! The newest libsoup came out the other day and since then I have not had another crash. I don't know what you did, but thank you! For me this problem has been resolved. $ rpm -qa | grep libsoup libsoup-2.2.93-1.fc5.1 $ rpm -qa | grep evol evolution-2.6.1-1.fc5.2 evolution-connector-2.6.1-1.fc5.1 evolution-connector-debuginfo-2.6.1-1.fc5.1 evolution-data-server-debuginfo-1.6.1-1.fc5.2 evolution-webcal-2.4.1-3.2 evolution-debuginfo-2.6.1-1.fc5.2 evolution-data-server-1.6.1-1.fc5.2
Ah, this is that bug then. Great. Fixed in 2.2.93. *** This bug has been marked as a duplicate of 342545 ***