Version: Version 1.9.1 (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages OS: Linux Apologies about the vagueness of this report. Occasionally my laptop locks when logging out of KDE (due largely to some problems with the ATI drivers), and I end up having to hard reset it. Unfortunately when I restart and log back into KDE, and fire up Kontact/Kmail it appears to have trashed the dimap cache sufficiently that it refreshes it from the server. This is strange as usually I have actually quit Kontact before trying to logout. I'd guess it was some state that is cached and not being sync'd until KDE logout. This is a fairly major problem for me as my mailboxes amount to 250mb, it takes forever to rebuild.
Happened to me too
I had the "pleasure" of observing this several times during the last weeks. From this I could observe the following steps of corruption: - 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.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.
(In reply to Laurent Montel from comment #3) > Thank you for taking the time to file a bug report. > > KMail2 was released in 2011, and the entire code base went through > significant changes. We are currently in the process of porting to Qt5 and > KF5. It is unlikely that these bugs are still valid in KMail2. > > We welcome you to try out KMail 2 with the KDE 4.14 release and give your > feedback. Thanks for looking into this. I'm sure you will understand that after not seeing any reaction on a bug of this criticality for many years, I've long ago abandoned KMail in favour of another mail client. I liked KMail but it simply wasn't reliable enough for me. Meanwhile I see no reason migrating back to a tool that *may* have become better.