Version: unspecified OS: Linux I can't download any messages after moving to kmail2. The folders appear to have been migrated correctly as I can view all of my folder as well as the messages contained in them. Regardless of whether the check for new msgs is launched at startup, manually or restarted, it always gets stuck at 'Preparing for transmission with XXX' (the actual English translation may be slightly different, sorry..) When launched from the console, there is the following output: $ kmail kmail2(3662)/kdeui (Wallet): The kwalletd service has been disabled kmail2(3662)/kdeui (Wallet): The kwalletd service has been disabled kmail2(3662)/kdeui (Wallet): The kwalletd service has been disabled kmail2(3662)/kdeui (Wallet): The kwalletd service has been disabled kmail2(3662)/kdeui (Wallet): The kwalletd service has been disabled kmail2(3662)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! kmail2(3662)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! kmail2(3662): Error while fetching items. 103 "Unknown error. (Cannot list root collection.)" It seems to be the same issue as described in http://forum.kde.org/viewtopic.php?f=20&t=90234 but I haven't been able to find a registered bug report for this. Reproducible: Always OS: Linux (x86_64) release 2.6.39-gentoo-r1 Compiler: x86_64-pc-linux-gnu-gcc ----- Version info (I couldn't select this version in the KDE bugs app version dropdown): $ kmail -v Qt: 4.7.3 KDE Development Platform: 4.6.4 (4.6.4) KMail: 2.1.0
I am also experiencing the same problem with kmail2 on Arch Linux.
Recreating the accounts solved the issue for me
can not reproduce with KDE 4.10
This bug is still present in 4.10 on my system (Arch Linux x86_64). I've recreated the Akonadi database, I've recreated all my accounts and I've recreated the wallet for the passwords, but this didn't work. I've done some experiments which may help to solve this bug. On my system, Chromium and Kmail are normally launched when I log in. They both use Kwallet. This situation always triggers the bug. However, if I shutdown Chromium or Kmail before I log out and start them manually after the next login, then everything works fine. In the first situation, when the bug is triggered, restarting Chromium, Akonadi, and/or Kmail doesn't help. What does help is aborting the mail fetch activities in Akonadi Console and killing the kwallet daemon. In previous versions (before 4.10), I could work around the problem by disabling the mail check at startup. In 4.10, Kmail asks for a password immediately when it is launched, so this workaround no longer works.
So it seems all boils down to a problem with the access to the wallet. The password which is asked by kmail 4.10 is the one for your wallet ? Did you try to not define a password for the wallet at all ?
The password is indeed the one for the wallet. Without a password, everything works fine. I also noticed that when this bug is triggered, Kmail asks for the password at launch and for every account when it starts trying to fetch the mail. In situations where the bug isn't triggered, Kmail asks for the password only once (at launch).
I can confirm the behaviour as described by Patrick for KDE 4.10 and 4.10.1 with openSUSE 12.2 and openSUSE 12.3 binaries.
I found the following lines in .xsession-errors: [2364:2386:0807/120437:ERROR:object_proxy.cc(532)] Failed to call method: org.kde.KWallet.open: object_path= /modules/kwalletd: 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. [2364:2386:0807/120437:ERROR:native_backend_kwallet_x.cc(838)] Error contacting kwalletd (open) This bug might be related to bug 254198.
It seems to be fixed in 4.11.2, so it probably was a duplicate of bug 254198 (at least in my case).
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.