Version: unspecified OS: Linux The auth handler gets stuck in a bit of a loop if "canTryAgain" is false and the password in the wallet is wrong. It will load the password from the wallet, try it - find it fails. Then exit. Forcing canTryAgain to true, resulted in the auth-handler waiting from a response from the second auth that never arrives (which sound like a gabble bug, it should at least fail). Subsequent attempts Reproducible: Sometimes Steps to Reproduce: Create a new google account (just choose any username and password) Actual Results: Account consistently fails to connect with "Authentication failed" Expected Results: Password prompt after second attempt
[23:15] <drdanz> d_ed: we could try this way... besides passwords, in kwallet it is possible to save other stuff (I still don't know how but it looks like that it is possible) so we could save a map per account containing a value "LastLoginSuccesful" and if it is false popup the prompt
Git commit d8c783e45f3adce0b7203f08e667a9fef2941980 by Daniele E. Domenichelli. Committed on 27/10/2011 at 02:12. Pushed by ddomenichelli into branch 'master'. Save lastLoginFailed entry in KWallet This allows to prompt for the password if canTryAgain is false and the stored password is false BUG: 284419 M +6 -1 sasl-auth-op.cpp http://commits.kde.org/telepathy-auth-handler/d8c783e45f3adce0b7203f08e667a9fef2941980