Re: Complete lockup in KMail

On Saturday, 7 January 2017 17:30:15 GMT Martin Steigerwald wrote:
> Am Samstag, 7. Januar 2017, 16:13:04 CET schrieb Peter Humphrey:
> > On Tuesday, 3 January 2017 19:43:19 GMT Martin Steigerwald wrote:
> > > Am Dienstag, 3. Januar 2017, 18:28:50 CET schrieb Peter Humphrey:
> > > > > I was stuck recently after a semi-failed upgrade.  After messing
> > > > > with
> > > > > the
> > > > > akonadi database for a few hours I finally just shut akonadi down
> > > > > ('akonadictl stop'), removed ~/.local/share/akonadi ('rm
> > > > > ~/.local/share/akonadi') followed by a start ('akonadictl start').
> > > > > The
> > > > > start will see that the database is gone and rebuild it from
> > > > > scratch.
> > > > 
> > > > Ah, now there used to be a trick whereby stoppint akonadi, removing
> > > > .local/ share/baloo (I think it was) and starting akonadi again
> > > > would
> > > > have the same effect. But with the current version(s) it has no
> > > > effect
> > > > at all. That directory stayed gone when I tried it. Thanks for the
> > > > tip.
> > > 
> > > The search database has moved to ~/.local/share/akonadi/search_db on
> > > splitting out mail indexing into an akonadi component (Akonadi
> > > Search).
> > 
> > So if I delete that directory and restart akonadi, will it rebuild all
> > the indexes?
> 
> Maybe not immediately, but eventually it will. Maybe it helps if you
> remove the "initialIndexingDone=true" from the (I think not yet to
> akonadisearch renamed) config file, or remove the file and let it
> recreate it.
> 
> ~/.config> cat baloorc
> [Akonadi]
> aborted=false
> agentIndexingVersion=4
> dirtyCollections=
> initialIndexingDone=true

Hmm. Mine is shorter:

$ cat .kde4/share/config/baloorc
[Akonadi]
agentIndexingVersion=4
initialIndexingDone=true

The mails got into such a mess that I've started again with another new user 
and imported from archive. I'm keeping a note of all the straws i see that I 
could clutch at!

Thanks Martin.

-- 
Regards
Peter