GNOME Bugzilla – Bug 634422
Evolution using exchange plugin, just hangs getting email
Last modified: 2010-12-05 16:18:26 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=650203 When starting up exchange, it will start looking for new mail, somtimes goes to 100% and then does nothing. Version-Release number of selected component (if applicable): 2-32 How reproducible: Start up evolution Steps to Reproduce: 1. Connect to an exchange email system 2. Let it start to get mail 3. Watch it just sit there and do nothing Actual results: Not Able to use Evolution instead of outlook Expected results: Able to use Evolution instead of outlook. Additional info: This is an upgrade of Fedora 13 to Fedora 14. Fedora 13 exchange still working fine. Have tried gdb debugging and loading in terminal. Shows nothing helpful. Just stops, still shows like it is trying.
+ Trace 224596
Thread 3 (Thread 0x9ddfab70 (LWP 5923))
Any ideas when can this be addressed? I think I must have open/closed Evo 20 times this morning alone... :-(
Created attachment 175099 [details] [review] proposed ls patch for libsoup; I'm not sure, but I would use the timed wait on the priv->cond, to test the connection itself again in some time manner - I chose 250 ms. From what I saw in the code, the priv->cond is signalled only from cancel_message function, and nowhere else. I though to add signalling on various other places, especially where the item's state is changed, but then I realized (though it's possible I overlooked something) that the process_queue_item cannot be called simultaneously for one item, thus the timed wait was my option.
Created attachment 175118 [details] [review] SoupSessionSync: fix messages getting stuck forever > but then I realized (though it's possible I > overlooked something) that the process_queue_item cannot be called > simultaneously for one item It doesn't matter; the cond is per-session, not per-item, so it will finish waiting when some other item signals it. This should fix it. I'm building f14 packages with this patch now to test, and I'll add a pointer to the RH bug when they're ready
Can't hang Evo here any more, after about 24 hrs of mistreatment of it. So, looks like this fixed it.
forgot to close this; fixed in 2.32.2