Thank you very much, Mr. Klapper. The question I have is how to cleanly get out of the problem without having to rename ~/.local/share/evolution/mail to (for example) ~/.local/share/evolution/mail.bad, restarting evolution and then moving all the folders under ~/.local/share/evolution/mail.bad/local into the new ~/.local/share/evolution/mail/local. I feel that I am "playing with fire" as my consulting business runs on the e-mail part of evolution, and loss of e-mail to/from clients would be a disaster. So far, other than lost time, I do not appear to have been burned. As noted in the bug report you referenced, this problem occurs when starting up evolution either after a reboot needed by system upgrade or after turning on my laptop for after it had been shut down for travel. John -----Original Message----- From: Andre Klapper <ak-47 gmx net> Subject: Re: [Evolution] evolution 3.20.5 fails again with lockup on opening "Generating message list" Date: Fri, 21 Oct 2016 15:33:50 +0200 On Thu, 2016-10-20 at 18:08 -0400, john@lauterbachandassociates wrote:What are next steps?I realize that I filed a bug report about that a while ago: https://bugzilla.gnome.org/show_bug.cgi?id=764044 Evolution shows no "lockup" here, it's merely that the stray "Generating message list" item does not allow exiting Evo cleanly. Last time we tried debugging it Milan was kind enough to provide debug packages but I've upgraded to a newer version since then. :-/ andre |