Bug 351701 - akonadi resources doesn't wait for kwallet5 with gpg key to open in 15.08.0
Summary: akonadi resources doesn't wait for kwallet5 with gpg key to open in 15.08.0
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-24 17:29 UTC by Daniel Eklöf
Modified: 2022-12-10 15:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Eklöf 2015-08-24 17:29:59 UTC
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').
Comment 1 Daniel Eklöf 2015-09-05 09:58:22 UTC
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.
Comment 2 Ben 2016-03-22 18:37:54 UTC
I think this is related to Bug #339767
Developer says he will "eventually fix it". Really hoping he will some day.
Comment 3 Björn Bidar (Thaodan) 2017-10-10 19:07:08 UTC
same issue for ktp/telepathy-kde
Comment 4 Justin Zobel 2022-11-10 08:52:28 UTC
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!
Comment 5 Björn Bidar (Thaodan) 2022-11-10 13:15:24 UTC
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
Comment 6 Bug Janitor Service 2022-11-25 05:15:59 UTC
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!
Comment 7 Bug Janitor Service 2022-12-10 05:13:16 UTC
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!