Ubuntu 7.04 updated, Evolution 2.10.1, i386 I have had a similar behavior today and I solved it by moving my mail/local/Inbox* files to another dir when evo and all helper programs were *not* running, starting evo, and then moving them back while it *was* running (this was accidental but it worked). It spat messages saying it was redoing the database, and it works fine now. I have a moderately large Inbox (500+MB), so it may be that while the file was copying it had time to make the dbs, and this might not work for smaller Inboxes. In that case just moving in the Inbox file itself (appears to be a normal mbox file) might do it.
I presume that the system crash I had yesterday happened while evo was writing the database or something, and the database was corrupt and caused the problem, which matches what's described above: CPU pegs as soon as the mail reader GUI is visible on screen, whether it's there or not when started. The mail GUI window does not refresh thereafter. It stays pegged for at least many hours, likely indefinitely. I did not check for a memory loop. Suggestion: Email is a critical ap, and this is not the first time I have had trouble with evo and messed-up databases. Others clearly are having similar problems. A user should be able to tell evo to validate and/or recover its databases as a startup option or separate program. Even better, also have it validate all dbs in some fashion on startup, or give itself an alarm and have it check the db being read if the alarm triggers during a database read. Simply being locked out of your email and calendar for hours while you troubleshoot is not an option, and troubleshooting in this manner risks losing mail. I have captured the corrupt files, though I will not post them publicly because they are large (500MB) and it's my private email. I can work with a developer, however. I don't know specifically which file is bad, but it's narrowed down to the Inbox* files. --jh-- -- Evolution hangs when I start it https://bugs.launchpad.net/bugs/13333 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
