Bug 261119 - Akonadi needs restarting after POP account password change
Summary: Akonadi needs restarting after POP account password change
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: POP3 Resource (show other bugs)
Version: 1.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-24 01:53 UTC by Valentin Rusu
Modified: 2010-12-25 00:28 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 Valentin Rusu 2010-12-24 01:53:53 UTC
Version:           2.0.89 (using KDE 4.5.85) 
OS:                Linux

I just changed my POP account password, on the ISP administration page.
After that, akonadi resource dialog popped up complainig about the server authentication failure.
I clicked "settings" and changed the password (that's the only thing I changed) then clicked OK.
Back to KMail, I clicked "check mail" but the login failure akonadi dialog keeped popping up. I re-entered the new password several times, checked that the new password was correctly stored in KWallet and finally I had the idea to quit KMail and issue a "akonadictl stop" before relaunching KMail and finally getting my mails.

The issue : I think KMail should somehow notify akonadi to re-read POP account settings after such a password change in the settings dialog.


Reproducible: Always

Steps to Reproduce:
Use an already configured POP account, using automatic periodic retrieval of mails.
Change password on the POP server side.
Wait for akonadi resource to popup stating "authentication failure".
Change settings and enter the new password.
Close the dialog box.
The akonadi resource will continue to popup after the configured interval.


Actual Results:  
Akonadi keeped using the old password.

Expected Results:  
Akonadi should have been told by KMail2 to use the new password.
Comment 1 Thomas McGuire 2010-12-25 00:28:45 UTC
I think this is fixed now with the commit a22620fa7944188921935ae2bfb53404dffa4305 I made today, please try a newer version.