Version: 1.7 (using KDE 3.3.1, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-2) OS: Linux (i686) release 2.6.9-1-686 When logging into KDE, kmail always start. Even if when previously logged out kmail wasn't running. If kontact was launched, it is relaunched (correctly) by session but then conflict with kmail. I deleted all my ~/.kde, then it was ok. I added back .kde/share/config/kmail.rc and .kde/share/apps/kmail then the strange behaviour reappears. Perhaps it is a debian packaging bug. It don't know how to solve it, I've tried all idea I had. Thanks for any help, Steph
Problem still there with version 1.7.1 (KDE 3.3.1)
it seems that this bug appears because korganiser is launched. If I remove the auto-launch of korganiser it kmail stops launching. I let the bug open as this behaviour should not happen. Thanks Stephane
AFAIK, this is a known problem. The first program which is using IMAP resources (like KOrganizer) causes KMail to start, because the IMAP resource code is closely coupled to KMail code, yet! This has been an annoying bug for several KDE versions now. I hope this will soon be fixed!
*** This bug has been confirmed by popular vote. ***
I see this in kdelibs-4.2.0-15.fc10.x86_64, kdepim-4.2.0-2.fc10.x86_64 using Fedora 10. It is kinda really annoying, any hints on how to work around this behavior is appreciated. Also, let me know how I can help finding out the source of this problem. Like in the above comments, I've made sure that kmail/kontact is not running when I log out, but when I log in, kwalletmanager says kmail is asking for permission, and when I open the wallet, kmail starts. I then have to close it, and sthen tart kontact. I too have seen this in earlier versions of KDE.
This was interesting: I logged in, kmail was automatically started, I quit it and then started "kopete" from a console: $ kopete kopete(3609)/kresources Kolab::KMailConnection::checkReply: D-Bus communication failed. Reply error is: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/Groupware'") Last interface error was: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/Groupware'") kopete(3609)/kdepimlibs (kabc): "Unable to open resource 'imap address book'!" Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. kopete(3609)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! kopete(3609)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "kopete_msn"'! kopete(3609)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! Calling appendChild() on a null node does nothing. So, I think this bug should be reassigned to "general" or some other KDE component. Maybe "kabc"? kdelibs-4.2.0-15.fc10.x86_64 kdepim-4.2.0-2.fc10.x86_64
I've noticed this too and it doesn't help that if you don't want the kmail at that time, it keeps asking the pwd over and over again, without giving a change to quit the whole program.
I've seen this problem less frequently after disabling the KOrganizer reminder daemon (ie. make it *not* start on login). Also, I read an interesting comment from Ingo Klöcker [1]: This problem did already exist in KDE 3.5. The problem is that both, KMail and Kontact provide the service DBUS/ResourceBackend/IMAP This is what I've got (Fedora Rawhide): $ find /usr -name '*.desktop' -print0 | xargs -0 grep 'DBUS/ResourceBackend/IMAP' /usr/share/applications/kde4/KMail.desktop:X-KDE-ServiceTypes=DBUS/ResourceBackend/IMAP,DBUS/Mailer /usr/share/kde4/servicetypes/dbusimap.desktop:X-KDE-ServiceType=DBUS/ResourceBackend/IMAP So, whenever an application wants to access an imap addressbook or imap calendar, this will result in kmail getting started (and not the dbusimap thingy). This is pretty consistent with what I am seeing - if I eg. try to syncronize my phone and kdepim using opensync, I get the same behaviour (first, close kontact/kmail): $ msynctool --sync mobile-kdepim Synchronizing group "mobile-kdepim" libopensync-kdepim-plugin(12827)/kresources Kolab::KMailConnection::checkReply: D-Bus communication failed. Reply error is: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/Groupware'") Last interface error was: QDBusError("", "") libopensync-kdepim-plugin(12827)/kdepimlibs (kabc): "Unable to open resource 'imap address book'!" libopensync-kdepim-plugin(12827)/kresources Kolab::KMailConnection::checkReply: D-Bus communication failed. Reply error is: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/Groupware'") Last interface error was: QDBusError("", "") Member 2 of type kdepim-sync had an error while connecting: Unable to lock addressbook for writing. Member 1 of type syncml-obex-client had an error while connecting: Bluetooth connect error All clients have disconnected The sync failed: Unable to connect one of the members Error while synchronizing: Unable to connect one of the members And KMail is started during this (failed) sync. Moreover (first close kmail/kontact): $ kabcclient -L kabcclient(13037)/kresources Kolab::KMailConnection::checkReply: D-Bus communication failed. Reply error is: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/Groupware'") Last interface error was: QDBusError("", "") kabcclient(13037)/kdepimlibs (kabc): "Unable to open resource 'imap address book'!" KMail is again started. (I also tried "konsolekalendar --view", but got a Segmentation fault) Now - how should I proceed in debugging/work around this? Should I modify /usr/share/applications/kde4/KMail.desktop to not include DBUS/ResourceBackend/IMAP? [1] http://thread.gmane.org/gmane.comp.kde.devel.pim/22948/focus=22949
KDE 4.3.0 update: Problem still exists.
*** Bug 97764 has been marked as a duplicate of this bug. ***
I've got the same problem since I upgraded to kde 4.12.0. I'm using Arch linux
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.