After upgrading to plasma 5.3.95 (including the new kf5-based akonadi+PIM applications) I created a kwallet5 using a GPG key (and therefore I *don't* use kwallet-pam - in case that matters). Now when logging in, several akonadi resources doesn't wait for me to unlock the wallet. I do get the unlock-wallet-dialog, but it seems the resources doesn't wait for it to close. kmail for example wants me to manually enter the password for my IMAP accounts. My google contacts/calendar resources on the other hand simply fails, and I have to manually restart them (which works because at this point, the wallet is opened). Reproducible: Always Steps to Reproduce: 1. Create a GPG-encrypted kwallet (kf5-version) 2. Create e.g IMAP resources. Google contacts and calendar has been seen to fail too. 3. Make sure passwords are saved in the wallet, and that e.g. kmail is set to automatically start at login. Then logout/login. 3. Alternatively (but not verified to trigger the bug...) close the wallet and start kmail manually. Actual Results: I'm asked to unlock my wallet. BUT, the akonadi resources doesn't wait for me to do so. Expected Results: The akonadi resources shouldn't fail/ask me to manually enter the password(s) until I have actually tried to unlock the wallet (or clicked 'cancel').
At least the google contacts and calendar resources fail in the same way too, regardless of whether the wallet is using a gpg key or blowfish password.
I think this is related to Bug #339767 Developer says he will "eventually fix it". Really hoping he will some day.
same issue for ktp/telepathy-kde
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
I think the issue is no longer present right now. In it's original state, but I've akonadi-ews showing 401 before the authentication token could be opened from kwallet. Br, Björn
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
I'm an Arch Linux user with KDE Plasma 6.0.5 and KDE Frameworks 6.2.0 and this problem persists. KMail waits until KWallet has been opened by entering the password. Unfortunately, the DAV Groupware Resource in Akonadi does not. Currently, I have to - unlock KWallet by entering the password - click away the password prompt for the DAV Groupware Resource Agent several times - restart the DAV Groupware Resource Agent via the Akonadi Console manually How can I ensure that only one password prompt is opened and all other Akonadi agents wait for KWallet? Having to constantly restart the agent manually is time-consuming.