search

google-code-export / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
2 stars 0 forks source link

twitter fails to connect, but will not completely disconnect/disable #162

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. enable twitter account
2. as soon as 'authentication error' message pops up, disable twitter account

What is the expected output? What do you see instead?
It is expected that the mbpurple plugin completely disconnect and not
attempt further logins.  However, there appears to be a bug and the account
does not disable itself, instead causing a continuous authentication loop
and the following error in the debug log:
(16:17:36) g_log: purple_account_disconnect: assertion
`!purple_account_is_disconnected(account)' failed

This error will spawn continuously when pidgin is changed to the 'offline'
state, until the process is killed.

What version of the product are you using? On what operating system?
mbpurple 0.2.4, pidgin 2.6.3

Please provide any additional information below.

Log Snippit:

(09:53:33) connection: Connecting. gc = 0xaaae920                         

(09:53:33) twitter: twitter_login                                         

(09:53:33) twitter: mb_account_new                                        

(09:53:33) twitter: creating id hash for sentid                           

(09:53:33) twitter: getting user/host                                     

(09:53:33) tw_util: twitter_get_user_host                                 

(09:53:33) tw_util: username = ##ak_hepcat##                              

(09:53:33) tw_util: host (config) = twitter.com                           

(09:53:33) twitter: user_name = ak_hepcat                                 

(09:53:33) twitter: path = /account/verify_credentials.xml                

(09:53:33) mb_net: new: create conn_data = 0xaa7d210                      

(09:53:33) mb_net: registered new connection data with MbAccount          

(09:53:33) mb_net: NEW mb_conn_process_request, conn_data = 0xaa7d210     

(09:53:33) mb_net: connecting to twitter.com on port 443                  

(09:53:33) mb_http: prepared packet = GET /account/verify_credentials.xml
HTTP/1.1                                                                  

Authorization: Basic YWtfaGVwY2F0OmFic2NvbmR2OA==                         

Host: twitter.com                                                         

User-Agent:curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g
zlib/1.2.3.3 libidn/1.1                                                   

Accept: */*                                                               

(09:53:33) util: requesting to fetch a URL
(09:53:33) dns: DNS query for 'fwmgr.gci.net' queued
(09:53:33) twitter: looking for twitgin             
(09:53:33) twitter: registering twitgin-replying-message signal
(09:53:33) dns: Created new DNS child 14818, there are now 1 children.
(09:53:33) dns: Successfully sent DNS request to child 14818          
(09:53:33) dns: Got response for 'fwmgr.gci.net'                      
(09:53:33) dnsquery: IP resolved for fwmgr.gci.net                    
(09:53:33) proxy: Attempting connection to 209.165.131.200            
(09:53:33) proxy: Connecting to twitter.com:443 via fwmgr.gci.net:8888
using HTTP
(09:53:33) proxy: Connection in progress                                  

(09:53:33) proxy: Connected to twitter.com:443.                           

(09:53:33) proxy: Using CONNECT tunneling for twitter.com:443             

(09:53:33) proxy: HTTP proxy connection established                       

(09:53:33) proxy: Connected to twitter.com:443.                           

(09:53:33) nss: subject=CN=twitter.com,OU=Domain Control Validated -
RapidSSL(R),OU=See www.rapidssl.com/resources/cps
(c)09,OU=GT09721236,O=twitter.com,C=US issuer=CN=Equifax Secure Global
eBusiness
 CA-1,O=Equifax Secure Inc.,C=US                                          

(09:53:33) nss: subject=CN=Equifax Secure Global eBusiness CA-1,O=Equifax
Secure Inc.,C=US issuer=CN=Equifax Secure Global eBusiness CA-1,O=Equifax
Secure Inc.,C=US                                   
(09:53:33) certificate/x509/tls_cached: Starting verify for twitter.com   

(09:53:33) certificate/x509/tls_cached: Checking for cached cert...       

(09:53:33) certificate/x509/tls_cached: ...Found cached cert              

(09:53:33) nss/x509: Loading certificate from
/home/leif/.purple/certificates/x509/tls_peers/twitter.com                

(09:53:33) certificate/x509/tls_cached: Peer cert matched cached          

(09:53:33) certificate: Successfully verified certificate for twitter.com
(09:53:33) util: request constructed
(09:53:33) util: Response headers: 'HTTP/1.1 504 Gateway Timeout
Via: Cachet/0.91
Connection: close
Server: Jetty(6.1.21)

'
(09:53:33) mb_net: mb_conn_fetch_url_cb: url_data = 0xaa7d290
(09:53:33) mb_net: going to call handler
(09:53:33) connection: Connection error on 0xaaae920 (reason: 0
description: Authentication error)
(09:53:33) mb_net: handler returned, retval = -1
(09:53:33) mb_net: handler return -1, retry 1
(09:53:33) mb_net: NEW mb_conn_process_request, conn_data = 0xaa7d210
(09:53:33) mb_net: connecting to twitter.com on port 443
(09:53:33) mb_http: prepared packet = GET /account/verify_credentials.xml
HTTP/1.1
Authorization: Basic YWtfaGVwY2F0OmFic2NvbmR2OA==
Host: twitter.com
User-Agent:curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g
zlib/1.2.3.3 libidn/1.1
Accept: */*
X-Twitter-Client: mbpidgin
X-Twitter-Client-Version: 0.1
X-Twitter-Client-Url: http://microblog-purple.googlecode.com/files/mb-0.1.xml
Connection: Close

Original issue reported on code.google.com by ak.hep...@gmail.com on 19 Oct 2009 at 6:01

GoogleCodeExporter commented 9 years ago 
This is a severe error! The plugin attempts to login every 1 or 2 seconds when
authentication fails. It will not wait for the user input from Pidgin popup 
"retry"
but will retry by itself until the process is killed.
Additionally, it will lock you out from your Twitter account for some time 
because of
too many false login attempts.

Original comment by Drah...@googlemail.com on 10 Dec 2009 at 7:59

GoogleCodeExporter commented 9 years ago 
This looks very much like Issue 157:
http://code.google.com/p/microblog-purple/issues/detail?id=157

Merge?

Original comment by sinisa.d...@gmail.com on 13 Dec 2009 at 8:40

GoogleCodeExporter commented 9 years ago

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