[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: KMail/Akonadi grief
From:       Anders Lund <anders () alweb ! dk>
Date:       2019-11-12 9:49:23
Message-ID: 3536345.eng6iuo8oy () elias
[Download RAW message or body]

Now here is a thought for kmail developers:

Going offline and back online makes the BSOD go away.

When the BSOD id shown, akonadi must waiting for something that never happens. 
Going offline clears the wait, and going online again what we are actually 
waiting for - message displayed - can happen.

So what ever action is not answering needs to be fixed. Drop it, do it later, 
whatever allows kmail to do what it is supposed to, which is display the 
message the user wants to read.

Kindly
Anders

mandag den 11. november 2019 21.07.51 CET skrev Anders Lund:
> mandag den 11. november 2019 16.55.55 CET skrev Paul Vixie:
> > Anders Lund wrote on 2019-11-11 07:49:
> > > Hi,
> > > 
> > > I switched akonadi to using postgresql, and it definately feels like it
> > > operates more smoothly than before.
> > > 
> > > But I still get the KMail BSOD (the "fetching folder content..." screen)
> > 
> > i have bound "toggle online/offline" to control-space, and when i see
> > that screen, i hit control-space twice, and 90% of the time it
> > unfreezes. the other 10% of the time i have to stop kontact/kmail,
> > "killall" kontact/kmail from a shell, and run "akonadictl fsck" then
> > "akonadictl vacuum" then "akonadictl stop". then i restart kontact/kmail
> > and it restarts akonadi and all is well again for several hours.
> 
> This is actually a very useful tip, the fastest way to recover I have tried
> yet. Thanks a lot! :)
> 
> --
> Anders




[prev in list] [next in list] [prev in thread] [next in thread]