No.. I haven't. I'm really not interested in a new initialization of the kontact / akonadi / neopunk system. I am interested in my established installation and configuration. However.... If you read one of my previous post you will notice a workaround. And if you read the KDE Bugs report, you will see that it is a problem that has existed since at least 4.4 Beta with the an accurate pointer to the developers as to where the problem lies. It just wasn't fixed before final. And hence the workaround that was pointed to in the Bug report and outlined in the bugzilla report and in a previous post here. The only thing that I might try is to blow away my akonadi configuration and see if that helps. However, I shouldn't have to do this everytime there is an upgrade. Its one of those things that should never be an issue because of the nature of the data stored in Akonadi. If I was dealing with alpha, beta, even RC... OK its my fault... But again... this is gold and my data is important to me. Eli Quoting Sven Lankes <sven at lank.es>: > On Thu, Feb 11, 2010 at 10:35:22AM +0200, Eli Wapniarski wrote: > >> As posted previously >> https://bugzilla.redhat.com/show_bug.cgi?id=563789 >> https://bugs.kde.org/show_bug.cgi?id=218369 > > Thanks. I must have missed those. > > Kmail and Kontact start up just fine for me so this might well be an > issue with a configuration from 4.3 that breaks 4.4 (wouldn't be the > first time). > > Have you tried creating a new user on your system and reproducing it > using that user? > > -- > sven === jabber/xmpp: sven at lankes.net > _______________________________________________ > kde mailing list > kde at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/kde > New to KDE4? - get help from http://userbase.kde.org > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
