Description of problem: I am getting a series of camel-warnings when starting evolution. I attempted a reboot of the machine to be sure that all of the latest patches were being used and that did not resolve the issue. Version-Release number of selected component (if applicable): 2.2.3-2.fc4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: several camel warnings, then evolution starts and appears to be running normally though at this time I have not tested extensively. Expected results: Additional info: [~] [5:12pm] [jam@eros] % evolution es menu class init adding hook target 'source' (evolution:2859): camel-WARNING **: Invalid root: '/home/jam/.evolution/mail/local/Drafts.ibex.index' (evolution:2859): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:2859): camel-WARNING **: block size: 1024 (1024) OK (evolution:2859): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:2859): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:2859): camel-WARNING **: flags: unSYNC (evolution:2859): camel-WARNING **: Invalid root: '/home/jam/.evolution/mail/local/Outbox.ibex.index' (evolution:2859): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:2859): camel-WARNING **: block size: 1024 (1024) OK (evolution:2859): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:2859): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:2859): camel-WARNING **: flags: unSYNC
prior to rebooting the machine, I would get all of the above camel warnings, followed by a segfault of evolution. now, things seem to be a little more stable (no segfault at startup), but I have not tried sending out an email yet.
Thanks for filing this bug report. I'm sorry that it has gone for so long without activity; it was incorrectly assigned to me by bugzilla. Reassigning to mbarnes; once again, my apologies for my lack of activity on this bug.
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
Reporter, could you please reply to the previous question? If you won't reply in one month, this bug will be closed as INSUFFICIENT_DATA. Thank you.
Closing as INSUFFICIENT_DATA.