Version: (using KDE 4.4.1) Installed from: openSUSE RPMs When I have the akonadi resource activated in the system settings I can no longer start kmail or kontact and have to kill it. I was not logged out between stopping and starting kontact/kmail. When I start kmail from the console wile the akonadi resource is activated I get errors like: kaddressbook(9183)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" kmail(9350)/nepomuk (library) <unnamed>::GlobalModelContainer::init: Failed to connect to Nepomuk server via local socket "/home/fietze/.kde4/share/apps/nepomuk/socket" kmail(9350)/nepomuk (library) <unnamed>::GlobalModelContainer::init: Connecting to local socket "/home/fietze/.kde4/share/apps/nepomuk/socket" It seems that the first mail is read from /var/spool/mail into the inbox, and then kmail hangs. When killing kmail, it does not react to any key pressed or the mouse, and trying to start it again, the same thing happens and this first mail appears a second time in the inbox. As soon as the akonadi resource is deactivated everything is fine. This bug can be reproduced on two machines, one at home and one at the company. But I cannot force this behaviour by stopping kmail, sending myself a small mail locally (using "mail"), activating the akonadi resource and starting kmail again. Hmmm? Tomorrow morning I will trace all output of kmail under clean condtitions and a hopefully filled up /var/spool/mail, and I'll attach that to this bug report.
Can this be caused by having the original kaddressbook std.vcf and the akonadi resource acivated at the same time in the system settings kontact resource window (not the akonadi manage address book sources dialog). Do I just have to add the old std.vcf in akonadi manage address book sources dialog only if I want to use that as well, and only there, having just the akonadi resource been active and used in the configure KDE resources dialog of the system settings?
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.