Bugzilla – Bug 118388
Evolution hangs when accessing local mbox stored mails
Last modified: 2005-11-21 04:50:20 UTC
I have a hierarchy of local mbox folder. When using Evolution to access them, Evo hangs after looking at just a few mails. The status bar displays 'Retrieving Message 1185 (...) but the message is never shown. Menus etc are still responding, however with no effect, as it seems to be waiting for the pending message. Exiting Evo doesn't work either. The only to quit is to call 'evolution --force-shutdown' from a different terminal. STDOUT gives tons of messages like this: ** (evolution:3572): WARNING **: Serious fd usage error 15 ** (evolution:3572): WARNING **: Serious fd usage error 13 ** (evolution:3572): WARNING **: Serious fd usage error 14 ** (evolution:3572): WARNING **: Serious fd usage error 12 ** (evolution:3572): WARNING **: Serious fd usage error 10 ** (evolution:3605): WARNING **: Serious fd usage error 15 ** (evolution:3605): WARNING **: Serious fd usage error 13 ** (evolution:3605): WARNING **: Serious fd usage error 14 ** (evolution:3605): WARNING **: Serious fd usage error 12 ** (evolution:3605): WARNING **: Serious fd usage error 10 (evolution:3332): e-canvas.c-CRITICAL **: e_canvas_item_grab_focus: assertion `GTK_WIDGET_CAN_FOCUS (GTK_WIDGET (item->canvas))' failed (evolution:3332): e-canvas.c-CRITICAL **: e_canvas_item_grab_focus: assertion `GTK_WIDGET_CAN_FOCUS (GTK_WIDGET (item->canvas))' failed
Created attachment 50657 [details] Fix for the camel-lock-helper issue Fix committed in the stable branch for gnome-2-12 and would be available in 2.4.1 release. Patch attached for Autobuild updates, if required
Marking this as closed.
reopening. Just the existance of a path (which I appreciate!) doesn't fix it for SL10.0. Are there updates available for SL10.0 (Evolution 2.4.0), and where can people get them?
Could you please approve the attached patch to be made available through SL10 Updates.
Andreas product, Andreas has to approve...
Ok, aproved. SWAMP-ID: Maintenance-Tracker-2402
Submitted for 10.0. Stable will get the fix with next weeks update.