Bug 269230

Summary: Open Accounts KCM when account authentication fails
Product: [Unmaintained] telepathy Reporter: Alin M Elena <alinm.elena>
Component: contactlistAssignee: Martin Klapetek <mklapetek>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: kde-telepathy-bugs, kde, mklapetek
Priority: NOR    
Version: git-latest   
Target Milestone: 0.4.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alin M Elena 2011-03-23 14:15:52 UTC 
Version:           git-latest (using Devel) 
OS:                Linux

when authenthification fails for an account, the configure window for the account should be displayed.



Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.38-27-desktop
Compiler: gcc
Comment 1 David Edmundson 2011-03-25 15:38:06 UTC 
I'm not sure anything should automatically pop up. That has risk of being annoying, especially if it doesn't explain the problem.

My thoughts:
 - The Accounts KCM should start automatically trying to connect you when you make a new account (that was on a todo list somewhere) at which point this issue becomes a lot less important (but still valid)

 - The contact list needs to display that it can't connect for /any/ issue not just auth fails, but the server being invalid refusing connections etc. Ideally with the same error string as appears in the accounts KCM.

 - we need to a link to load up the correct account configure. Technically I think the contact list /could/ embed the dialog, OR we add a mechanism to the accounts KCM to look for command line args and open the relevant dialog.

Make sure to liaise with the account KCM people.
Comment 2 Martin Klapetek 2011-03-25 16:05:54 UTC 
Yes, I agree. My idea wasn't exactly to open accounts kcm in case of auth fails, but to let the user know via the messageFrame and offer him to open the accounts kcm for additional config. I like the idea of loading the particular account config by passing some arg. 

Who are the account kcm people btw?
Comment 3 David Edmundson 2011-09-20 13:30:32 UTC 
With the SASL handler this is now obsolete. This should keep prompting for passwords until it works.