Bug 333602 - Akonadi keeps asking for kwallet password
Summary: Akonadi keeps asking for kwallet password
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.13
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-18 22:55 UTC by Coacher
Modified: 2018-02-01 09:51 UTC (History)
3 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 Coacher 2014-04-18 22:55:35 UTC
Hello.

I have 3 online IMAP akonadi resources on 3 different servers. When I start akonadi from console (`akonadictl start`) or from systemsettings, it prompts for my kwallet password and then (after I type in a valid password) it asks for the password on each mailbox check (mail check interval is 10 minutes for all 3 resources). My kwallet is set to auto close after 25 minutes of idle and when all applications that use it are closed. Akonadi is not stopped obviously when this happens. However, kwallet is closed shortly after mail check as its systray icon disappears.

Please fix.

Reproducible: Always

Steps to Reproduce:
1. Start Akonadi with IMAP resource
2. kwallet password prompt appears
3. Input a valid password
4. Leave Akonadi running
Actual Results:  
Akonadi keeps asking for password on every mailbox check.

Expected Results:  
Akonadi is not asking for password on every mailbox check after I gave it once.
Comment 1 Coacher 2014-10-19 23:51:36 UTC
Ping.

Still present with 4.14.2.
Comment 2 Denis Kurz 2017-06-23 20:04:59 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:51:28 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.