Version: 1.13.5 (using KDE 4.5.1) OS: Linux When I try to run KMail, it immediately exits after printing a couple of lines of warning messages. Reproducible: Always Actual Results: $ kmail Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) "/usr/bin/kmail(1868)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/kmail(1868)" Soprano: "QLocalSocket::connectToServer: Invalid name" "/usr/bin/kmail(1868)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/kmail(1868)" Soprano: "QLocalSocket::connectToServer: Invalid name" "/usr/bin/kmail(1868)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" "/usr/bin/kmail(1868)" Soprano: "QLocalSocket::connectToServer: Invalid name" kmail(1868) KMFolder::updateIndicatorIcon: Could not read image from "" kmail(1868) KMFolder::updateIndicatorIcon: Could not read image from "" kmail(1868) KMFolder::updateIndicatorIcon: Could not read image from "" kmail(1868) KMFolder::updateIndicatorIcon: Could not read image from "" QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance() kmail(1868)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail(1868)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: <unknown program name>(1867)/: Communication problem with "kmail" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "
I think the underlying cause of this bug might be bug 266228: a problem with kwallet. But KMail really only needs the wallet to get my IMAP password. It seems strange that not being able to get the password would cause the app to lose all functionality, when at a minimum it still has all the local folders to work with. Even better, I could have been asked for the password to the mail server if there were problems retrieving from the wallet.
Created attachment 66116 [details] KMail output I am seeing this as well with KMail 4.7.3 (on KDE 4.7.3), akonadi-server 1.6.2, nepomuk 4.7.3 with Gentoo. Aknoadi has previously asked to enter a password for the one mailbox where it changed, so my assumption would be that the KDE Wallet works in a way.
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.