Created attachment 68796 [details] ikage of tripled directory structure Version: 4.7 (using KDE 4.7.4) OS: Linux Opened Kmail this morning all looked fine. Left machine running came back after 3 hours and the directory struture has trippled! I now have the original directory structure, one called local folders and one called akonadi mail resource! These two new directory structures are completely void of any mail but they are exact duplicates of the original local folders created by kmail. It's as if they are ghosts of the original structure minus all the mail in the real local mail folder. Reproducible: Always Steps to Reproduce: See screenshot attachement Expected Results: A single directory structure that does NOT triplicate itself OS: Fedora 16 (x86_64) release 3.2.5-3.fc16.x86_64 Compiler: gcc
What do you do ? You imported email from kmail 1 ?
I've been running the 4.7.4 software for almost a week before this happened. Yes my old mail was imported but that was a an entire week ago with no problems. When you go into the akonadi manager all this stuff just started showing up. There are serious problems going on with Kmail since it port to kmail2. Goggle Kmail and you'll see there are thousands of complaints on things that are happening with people trying to figure out how to fix it on their own.. As I stated Kmail has been working fine for an entire week with no problems of duplicate folders showing up at all, then yesterday all of a sudden these new folders show up out of nowhere, WHY? You can't remove them because they just magically come back. Even if I delete then from the akonadi software it recreates them by itself and adds them back into Kmail. This is a serious bug that needs to be fixed!
Yes if it's a bug it needs to be fix, right. But how I reproduce it ???? I use kmail2 from 1 year and I don't see this bug...
On Thursday, February 16, 2012 03:13:00 PM Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=294083 > > > > > > --- Comment #3 from Laurent Montel <montel kde org> 2012-02-16 15:12:59 --- > Yes if it's a bug it needs to be fix, right. > But how I reproduce it ???? > I use kmail2 from 1 year and I don't see this bug... That's a good question? From what I can tell by looking through the various directories that akonadi points to, it seems it is an akonadi issue. Now if it is a back end problem with the database or not is yet another question! Now as I have stated, I went in to the akonadi configuration module in system setting and followed the paths in the file system and checked and they do exist but the are empty. So I went back into akonadi configuration and deleted those entries and before I could stop the akonadi service it recreated the entry I just deleted out of thin air. This should not happen. I do have program experience but it is windows based using VB 6 enterprise. So what I did was delete the directories that akonadi was pointing to, then deleted the resource out of akonadi configuration and before I could stop the akonadi service it recreated the entire resource yet again right down to the file directory in the system. Something is very wrong and from what I've seen it appears to be in the back end and the akonadi server itself. Hope this helps. The machine I'm currently using I'm going to upgrade to 4.8 but if you want I have another laptop that I can configure to match the configuration of this one after I clean it all up of old data which may take some time since I'm going away for a week for my 25th anniversary. Let me know if you want me to assist further in tracking down this ugly bug. My current system is Fedora 16 running the KDE 4.7.4 compilation with no other desktop software installed!
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.