GNOME Bugzilla – Bug 337355
Evolution 2.6.0-1 freezes under FC 5 when accessing MS Exchange server
Last modified: 2008-01-11 10:20:02 UTC
Distribution: Fedora Core release 5 (Bordeaux) Package: Evolution Priority: Normal Version: GNOME2.14.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Evolution 2.6.0-1 freezes under FC 5 when accessing MS Exchange server Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified Description: Description of Problem: After updating FC4 to FC5 Evolution cannot access mails stored on an Exchange server. Steps to reproduce the problem: 1. Start evolution 2. "Evolution crashed" message appears. Click on "Restart application" 3. Click on Exchange mail folder Actual Results: The number of unread messages is displayed correctly but Exchange fails to load the mail headers Expected Results: Mail folder should be loaded and displayed properly. How often does this happen? Always Additional Information: ------- Bug created by bug-buddy at 2006-04-05 12:34 -------
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. In your case, installing bug-buddy, and selecting Inform Developers should do the trick.
Thanks for your quick reply. A protocol of a gdb session is listed below: [jselzer@localhost ~]$ gdb evolution GNU gdb Red Hat Linux (6.3.0.0-1.122rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/evolution Reading symbols from shared object read from target memory...(no debugging symbols found)...done. Loaded system supplied DSO at 0xb3f000 (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 -1208432448 (LWP 6337)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) CalDAV Eplugin starting up ... [New Thread -1271682144 (LWP 6341)] [Thread -1271682144 (LWP 6341) exited] evolution-shell-Message: Killing old version of evolution-data-server... Detaching after fork from child process 6345. Detaching after fork from child process 6347. Detaching after fork from child process 6349. Detaching after fork from child process 6351. Detaching after fork from child process 6353. Detaching after fork from child process 6355. Detaching after fork from child process 6360. (evolution:6337): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1271682144 (LWP 6361)] [New Thread -1282188384 (LWP 6362)] [Thread -1282188384 (LWP 6362) exited] [New Thread -1282188384 (LWP 6363)] [New Thread -1293071456 (LWP 6364)] [New Thread -1303565408 (LWP 6365)] [New Thread -1314055264 (LWP 6366)] [New Thread -1324758112 (LWP 6367)] [New Thread -1335321696 (LWP 6368)] [Thread -1335321696 (LWP 6368) exited] [New Thread -1335321696 (LWP 6392)] [New Thread -1407087712 (LWP 6393)] [New Thread -1419117664 (LWP 6400)] Program received signal SIGSEGV, Segmentation fault. ---Type <return> to continue, or q <return> to quit--- [Switching to Thread -1419117664 (LWP 6400)] 0x00daf4ea in camel_object_cast () from /usr/lib/libcamel-1.2.so.0 (gdb) thread apply all bt
+ Trace 67477
Thread 13 (Thread -1419117664 (LWP 6400))
stacktrace has some similarities to bug 332996, but description does not match...
This bug and http://bugzilla.gnome.org/show_bug.cgi?id=332996 might have some similarities. In both cases Evolution crashes before something can be done. After the restart, Evolution seems to work in my case. You can see the mail folder and all subfolders in the navigation window. Even the number of unread messages is displayed correctly, but in the main window nothing shows up. You can open pull-down menus and properly access menu items.
The problem seems not only to occur with Exchange servers but looks more general. I had the same problem after upgrading an Evolution installation with IMAP configuration. In my eyes Evolution crashes while trying to read the old account data. After erasing the .evolution directory and the gconf data and restarting Evolution, everything looks fine. So my current suggestion is to erase the old configuration and to re-enter it manually as a workaround.
from the traces it looks like the mailer issues we had on 2.6.0,1,2. Can you upgrae to 2.6.3 (without removing .evolution and gconf data) and check if exchange mailer works?
After upgrading to 2.6.3 things became much better. Evolution still loses connection to the Exchange background process or refuses to display fresh mail messages although it noticed them coming in, but usually a restart brings help. In short terms: I can use Evolution again. Thanks to whoever fixed this problem.
http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines Closing as OBSOLETE. Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.