GNOME Bugzilla – Bug 261850
Evo gets stuck "Storing folder 'personal/Inbox()'"
Last modified: 2006-05-10 05:04:01 UTC
Description of Problem: The 2-3rd new email after restart of Evolution gets stuck on Send. This is an Exchange account using connector. I create a new message and click send. It goes to the "Outbox" and waits while a message comes up on the bottom right corner saying "Storing folder 'personal/Inbox()'" and stays that way until I kill all Evolution processes and restart. Just started happening in the last 2-3 Evolution 1.5 devel snaps. Actual Results: Expected Results: How often does this happen? Every 2nd or 3rd new email. Additional Information: I am using Red Hat 9.0 with current(7/22/04) 1.5 devel snaps, including connector.
Hm... it might be crashing and getting stuck before it can pop up the crash dialog. Can you try running it under gdb? gdb /usr/libexec/evolution/1.5/evolution-exchange-storage (and type "run" at the gdb prompt) and then if it hangs, see if it's dropped you back to the gdb prompt, and if so, type "thread apply all bt" and copy all of the output (of the entire gdb session) into this bug. If it hangs, but doesn't drop you back to the gdb prompt, you can hit ^C to get a prompt and then do the "thread apply all bt" and it might give a hint as to what it's doing when it's hung...
I could never get it to actually crash. It just hangs forever. I then tried running all of Evolution in gdb, but it is now having another problem that I have seen before. When I click on the arrow to expand my Exchange mailbox it will not expand it, so I can't see any of my folders. There are no messages to the screen and it doesn't appear to have crashed. I restart a bunch of times, killing every Evolution process each time, but it won't let me expand it. I can't really remember how I got beyond this problem in the past. I will keep trying to get it to crash and give some info, but so far it just gets all kinked up and unusable. I did see these messages in gdb, but they don't seem to be related directly to the problem reported in this bug. (evolution-exchange-storage:29651): GLib-GObject-WARNING **: invalid (NULL) pointer instance (evolution-exchange-storage:29651): GLib-GObject-CRITICAL **: file gsignal.c: line 1861 (g_signal_connect_data): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (evolution-exchange-storage:29651): CRITICAL **: file e2k-context.c: line 1694 (e2k_context_bpropfind_start): assertion `hrefs != NULL' failed ** (evolution-exchange-storage:29651): CRITICAL **: file e2k-result.c: line 525 (e2k_result_iter_next): assertion `iter != NULL' failed ** (evolution-exchange-storage:29651): CRITICAL **: file e2k-result.c: line 599 (e2k_result_iter_free): assertion `iter != NULL' failed
are you still having problems with recent builds/snapshots? the warnings you quote are not related to the problem. they come from a different bug, which is fixed now. if this is still happening, but it doesn't happen when you're in gdb, another way to get a backtrace is to attach gdb after the process hangs. Run evolution normally, and when it hangs, type "ps aux | grep evolution-exchange | head -1", and then "gdb --attach PID" where PID is the second column of the ps output. Once it's read all the debug info and you get a (gdb) prompt, type "thread apply all bt".
I ended up having to stop using Evolution because of bugs like this one and others that happen in 1.4 as well. I just couldn't get any work done, as it would crash so often. I will try again with the latest snaps and see if it is better. I am beginning to think the connector has issues with our setup here, as I have seen the same types of crashes in both 1.4 and 1.5. Unfortunately we are a large company and I don't have any access to our Exchange settings or servers, except as an end-user.
Just updated to the latest snapshots and still have the problem. I tried the attach process approach and here is the output from the exchange-storage process and the data-server. exchange-storage process: (gdb) thread apply all bt
+ Trace 49661
Thread 1 (Thread 1097614816 (LWP 20156))
STDERR/STDOUT data: (evolution:20148): camel-WARNING **: Invalid root: '/user/builder/.evolution/mail/local/Sent.ibex.index' (evolution:20148): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:20148): camel-WARNING **: block size: 1024 (1024) OK (evolution:20148): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:20148): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:20148): camel-WARNING **: flags: unSYNC (evolution:20148): camel-WARNING **: camel_exception_get_id called with NULL parameter. asked to activate component_id `OAFIID:GNOME_Evolution_Addressbook_Component:1.5' (evolution:20148): eab-widgets-CRITICAL **: file e-addressbook-view.c: line 1857 (eab_view_discard_menus): assertion `view->view_instance' failed load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 load http 0 now=0 asked to activate component_id `OAFIID:GNOME_Evolution_Addressbook_SelectNames:1.5' in e_book_response_open in e_book_response_open in async_open_response in async_open_response in e_book_response_open in async_open_response (evolution:20148): libebook-WARNING **: "e_book_get_contacts" on book before "e_book_open"
What is your Exchange Server version? And what is the latest service pack you are having? Can you set the flag E2K_DEBUG=4 and run exchange-storage and paste the output here? Just guessing if this has anything to do with the server...
It looks like it gets stuck in a endless loop and it prints out this message over and over again: (evolution-exchange-storage:2729): libsoup-CRITICAL **: file soup-connection.c: line 689 (soup_connection_send_request): assertion `conn->priv->socket != NULL' failed I talked to our IT department and they are using Exchange 2003 Service Pack 1.
*** bug 266435 has been marked as a duplicate of this bug. ***
Open for too long. Any updates? Nathan: you ge any chance to try with latest builds? A lot of things have changed. Evolution-exchange is no more a seperate button. It is integrated into Evolution in a lot nicer way. Can you test and tell if you have these scenario now?
To be honest I had to abandon Evolution a long time ago. This bug never got very much attention, but made my system unuseable. I have since switched to Thunderbird with Outlook for calendaring on Windows. Sucks, but I have way to many meetings to dabble with Evolution anymore. Sorry! Good luck and I would say it is probably likely that you have fixed the root cause, but I couldn't tell you for sure. Thanks, Nathan
If possible give a try to latest stable version 2.6.x, lots of calendar fixes have gone in. There was a issue in libsoup wich was fixed in 2.4.x time. Since we can not replicated this anymore...I am closing this bug. Please reopen if you still see this issue.
Evolution supports IMAP too. I suggest you to try Evolution IMAP so that you can have an exchange account and IMAP account configured side-by-side and use IMAP whenever you face problems with exchange. You will get calendaring as well.