© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Re: Comment #110. The problem you describe happens only when you actually change a password... and you should know you need to change it in your email client(s) also, at that point.
The problem described by this bug is becomes annoying due to transient network issues, down servers, and the like.
If the solution to this bug discovers problems with some servers, systems, or environments in which it is impossible to detect the difference between a password change and a transient error, TB/SeaMonkey should err in handling the condition without prompting the user for a password... because most of the time it _hasn't_ changed. And if it has, the user should know to change it everywhere, not just on the server. OK, that's full circle. Repeat until you understand that the transient error prompting is much more annoying, to many more people, than the occasional user lockout.
That said, debugging your situation is appropriate, to verify whether or not there is an error in the logic that discriminates password errors from other errors.