GNOME Bugzilla – Bug 317215
Bug in Evolution-exchange
Last modified: 2005-10-26 20:09:20 UTC
Distribution: Ubuntu 5.10 (breezy) Package: Evolution Priority: Major Version: GNOME2.12.0 unspecified Gnome-Distributor: Ubuntu Synopsis: Bug in Evolution-exchange Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Each time I open my Evolution, it attempts to open my Exchange-inbox, leading to a crash in the exchange-connector. It was not like this from start, but have happened from time to time, and right now seems to happen each time I start evolution. Steps to reproduce the crash: 1. Start evolution 2. 3. Expected Results: Crash (Segfault, I assume) in Evolution-Exchange How often does this happen? Always Additional Information: Running Ubuntu Breezy, but have had similar issues in Hoary. May be related to running a laptop without a persistent network connection. 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) (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) [Thread debugging using libthread_db enabled] [New Thread -1232463360 (LWP 9715)] [New Thread -1234916432 (LWP 9716)] (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 63199
Thread 1 (Thread -1232463360 (LWP 9715))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-26 07:45 UTC ------- Bugreport moved from Evolution / Miscellaneous to Connector / Connector The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was ulrik.mikaelsson@canaldigital.se.
After updating Ubuntu Breezy, I were finally able to connect successfully again. However, after a few times reading my mail, I am now without working exchange integration again. Since it seems to be an irradict problem, I would guess at some timing issue.
On a sidenote, when I re-login, I can again connect to Exchange. I have tried just killing evolution-data-server evolution-alarm-notify and evolution-exchange-storage, but it does not seem to do the trick. What else is reset at re-login?
The crash seems to be happening in libsoup ?
Potentially, yes. However, from what I can read from the traces, a signal-handler is called, giving back contan HTTP/1.1 server. Features: * (Optionally) completely asynchronous * Automatically caches connections * SSL Support using GnuTLS * Proxy support, including authentication and SSL tunneling * Client support for Digest, NTLM, and Basic authentication * Server support for Digest and Basic authentication See the test programs in tests/ for simple examples of how to use the code, or evolution-data-server and evolution-exchange for more complicated examples. rol to evolution, right? If I understand it correctly, Evo-exchange uses libsoup for async http. This is naturally implemented using a callback that gets signalled as soon as the server replies. From what I understand from the traces, the error actually occurs in the callback? On a sidenote, Breezy recently upgraded my Evo, dont know from what but right now it's evolution-2.4.1-0ubuntu7, evolution-exchange-2.4.1-0ubuntu1 and evolution-data-server-1.4.1-0ubuntu3. After that upgrade, this bug seems to occurr less often. It stills happens but not as often, and I can once again USE Evolution at all.
*** This bug has been marked as a duplicate of 318252 ***