No subject


Wed Apr 17 12:44:40 BST 2019


- hard reset while kmail is running
- after next boot starting kmail does not succeed within a time frame of 
  several minutes.
- next start of kmail complains about a missing folder (I think it was a 
  "new" folder of one of my mail folders)
- at some point kmail pops up lots of error dialog (like one for each cached
  mail folder): 
  "The UID cache file for folder xzy could not be written. 
   There could be a problem with file system permissions".
- at that point the dimap folder was almost empty

Given the size of my dimap cache, it could well be that the first launch
of kmail doesn't show a window because it is busy deleting the dimap
cache. It might just be the time needed to kill over 70000 files.
This would also explain, why the next start was missing some folder.
I assume the supposed permission problem is also caused by a missing
directory (like holding nested mail folders).

To me this looks similar to bug 127562, only the trigger is definitely
different. Is it possible to make the solution for bug 127562 more
general to apply for arbitrary crashes as well?

Given that some part of my machine is quite unstable as of late and given
that downloading 2GB of imap cache takes several hours, this is a very
critical bug for me.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list