Twitgin got me locked-out of Twitter

[GoogleCodeExporter]

What steps will reproduce the problem?
Don't know. Sorry.

What is the expected output? What do you see instead?
Pidgin cannot login into my Twitter account. Tries more times than
specified in the Accounts->Modify->Advanced: "Maximum number of retry"
field. I think that as a consequence of this I got locked-out of Twitter. I
managed to get back in, but now I'm afraid to use the plugin again and risk
another lock-out.

What version of the product are you using? On what operating system?
0.2.4 in Pidgin 2.6.2 on WinXP SP3

Please provide any additional information below.
Since I haven't changed any preferences/options regarding my Twitter
account and connecting to it, I was almost certain the problem is with the
Twitter service. However, I googled it and found that I am not the only one
who experienced this
(http://www.overclock.net/linux-unix/536058-microblog-purple-not-working.html).

Original issue reported on code.google.com by gfn...@gmail.com on 29 Sep 2009 at 8:47

[GoogleCodeExporter]

Could you run pidgin in debug mode (pidgin -d) and see in the debugging log if 
verify
account return success. (lookfor verify_account)? Or you can send the debugging 
log
to us (Be warn! your passphrase will be encoded inside that log...)

Original comment by somsaks on 29 Sep 2009 at 9:10

[GoogleCodeExporter]

I ran pidgin -d several times and checked the logs, there was not one instance 
of
verify_account in there. 

Anyway, this is how I "solved" the problem. I ran pidgin, it immediately 
started to
complain about not being able to connect to twitter (which is expected behavior
because I got a new password after the lock-out), so I disabled the twitter 
account,
after which pidgin froze (!) and I had to kill the process. Then, I ran pidgin 
again
(now with twitter account disabled), updated the password for the twitter 
account and
enabled the account. Everything was back to normal and twitter account works
perfectly since then.

It seems like the whole time pidgin acted just as if the password was incorrect.
However, that was not the case. I changed the password *after* the problem 
appeared
and after the lock-out. Somehow resetting the password made pidgin happy.

If the problem reappears I'll give more information about this.

Original comment by gfn...@gmail.com on 29 Sep 2009 at 7:02

[GoogleCodeExporter]

I am also experiencing this issue (or a similar issue) on 0.2.4 on Pidgin 2.6.5 
on
Vista x64 SP2.

I am certain I had the right password, as I had just changed it to be sure, but 
it
still failed with authentication error. It repeatedly (and *very* quickly) 
tried to
login: the debug log grew by about 100k worth of HTTP headers in 20 seconds as 
it
tried to authenticate. Disabling the account and deleting it, or deleting it 
while
still enabled causes Pidgin to crash, but this does not occur if the account is
disabled, then Pidgin is restarted before deleting the account. This behavior is
repeatable.

Let me know if you need any further information to help track this down.

Original comment by tracy.p...@gmail.com on 1 Feb 2010 at 5:22

[GoogleCodeExporter]

Fixed in SVN now.

Original comment by somsaks on 25 May 2010 at 6:53

• Changed state: Fixed

[GoogleCodeExporter]

Issue 162 has been merged into this issue.

Original comment by andresen.nils@gmail.com on 7 Feb 2011 at 9:58