GNOME Bugzilla – Bug 268358
Switching to an Exchange Inbox causes Evolution to Crash
Last modified: 2005-02-14 09:27:35 UTC
Description: Description of the crash: Clicking on the inbox folder of the Exchange mailbox causes evolution and connector to crash. This is with Evolution 2.0.1 and matching connector - as shipped in Fedora Core 3 test 3 for x86_64 machines. In this case running on a Sun w2100z (Dual Opteron 246 machine with 2GB RAM). There are two mailboxes configured - one is IMAP/S, the other is Microsoft Exchange 2003. When started, evolution scans all folders for new mail - Personal Folders -> Inbox on the Exchange mail account shows Inbox (2). Clicking on it to show the message index immediately causes the crash. Steps to reproduce the crash: 1. Start evolution 2. Click on exchange inbox to see index of messages 3. Crashes Expected Results: See the message index for the Exchange Mail account Inbox. How often does this happen? All the time. Additional Information: Standard build as supplied on Fedora Core 3 test 3 for x86_64 which I've just installed. Debugging Information: Backtrace was generated from './evolution' (no debugging symbols found)...Using host libthread_db library "/lib64/tls/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)...[Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 3553)] [New Thread 1136654688 (LWP 3574)] [Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 3553)] [New Thread 1136654688 (LWP 3574)] [Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 3553)] [New Thread 1136654688 (LWP 3574)] [New Thread 1094711648 (LWP 3571)] [New Thread 1126168928 (LWP 3564)] [New Thread 1126168928 (LWP 3564)] [New Thread 1115683168 (LWP 3562)] [New Thread 1105197408 (LWP 3561)] [New Thread 1084225888 (LWP 3559)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00000030f680bf7a in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 51034
Thread 1 (Thread 182894220096 (LWP 3553))
This looks very much similar to 66342. Can you upgrade to evolution/connector 2.0.2 and see if this works [ the fix for 66342 was on libsoup, which you should be getting by upgrading to eov 2.0.2 ]
I've done the upgrade - found the appropriate versions were already on rawhide. Thus far I cannot pursuade Connector to talk to Exchange at all - it fails with an Authentication failure. I've checked via OWA (Webmail) and the password I'm using is correct.
Update - leave it a while and suddenly it's decided it can connect to Exchange. As soon as it finished scanning all the folders, it dumped core again. The diagnostics produced say: camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' camel-CRITICAL **: file camel-object.c: line 951 (camel_object_cast): assertion 'check_magic(o, type, TRUE)' failed This is with: evolution 2.0.2 evolution-connector 2.0.2 libsoup-2.2.1 and libsoup-2.2.0 installed (libsoup-2.2.0 seems to only be there for evolution-data-server) Regards, Bevis.
Looks like some progress :-) Anyway, could you please get a backtrace of that core you got ?. If you have the core, you could create the stack using gdb .. gdb <install/path>/evolution ./core (gdb) thread apply all bt Or for more information, please have a look at http://www.gnome.org/projects/evolution/bugs.shtml
OK, here is the output to standard out; traceback output follows: ephiny.ee.surrey.ac.uk 32% evolution loading error file /usr/share/evolution/2.0/errors/shell-errors.xml loading error file /usr/share/evolution/2.0/errors/mail-composer-errors.xml loading error file /usr/share/evolution/2.0/errors/addressbook-errors.xml loading error file /usr/share/evolution/2.0/errors/e-system-errors.xml loading error file /usr/share/evolution/2.0/errors/mail-errors.xml loading error file /usr/share/evolution/2.0/errors/calendar-errors.xml loading error file /usr/share/evolution/2.0/errors/filter-errors.xml (evolution:8290): e-error.c-WARNING **: No parent set, or default parent available for error dialog (evolution:8290): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:8290): camel-CRITICAL **: file camel-object.c: line 951 (camel_object_cast): assertion `check_magic(o, ctype, TRUE)' failed (evolution:8290): camel-WARNING **: Trying to check NULL OBJECT is OBJECT 'CamelObject' (evolution:8290): camel-CRITICAL **: file camel-object.c: line 920 (camel_object_is): assertion `check_magic(o, ctype, TRUE)' failed (evolution:8290): camel-CRITICAL **: file camel-object.c: line 774 (camel_object_ref): assertion `CAMEL_IS_OBJECT(o)' failed (evolution:8290): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:8290): camel-CRITICAL **: file camel-object.c: line 951 (camel_object_cast): assertion `check_magic(o, ctype, TRUE)' failed ------- Now for the traceback: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found)...Using host libthread_db library "/lib64/tls/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)...[Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 8290)] [New Thread 1136654688 (LWP 8299)] [Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 8290)] [New Thread 1136654688 (LWP 8299)] [Thread debugging using libthread_db enabled] [New Thread 182894220096 (LWP 8290)] [New Thread 1136654688 (LWP 8299)] [New Thread 1126168928 (LWP 8298)] [New Thread 1115683168 (LWP 8297)] [New Thread 1105197408 (LWP 8296)] [New Thread 1094711648 (LWP 8295)] [New Thread 1084225888 (LWP 8293)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00000037f7e0bf7a in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 51125
Thread 1 (Thread 182894220096 (LWP 8290))
The production release of Fedora Core 3 has provided an oportunity to retest version 2.0.2 of connector on both x86 and x86_64. The version 2.0.2 works perfectly on the x86 platform. It continues to fail as described above on the x86_64. THIS IS A x86_64 PLATFORM ISSUE. Just thought that confirmation would be useful in tracking down the problem. Regards, Bevis.
Created attachment 44546 [details] [review] might fix it
this patch might fix it. it looks related to the stub marshalling, and that has a definite 64 bit issue in it.
NotZed: Has this patch been checked in? I'm wondering whether I can write this off for purposes of tracking 64-bit bugs...
Yes this has been committed to gnome-2-8 branch [ and HEAD as well ]
Patch committed
Marking bug as verified as its not reproducible on my test setup. Reporter can reopen the bug if this bug is reproducible after testing this scenario with latest build/CVS code.