[Pidgin] #1410: After upgrading from pidgin-2.0.0beta7.exe -> pidgin-2.0.0.exe can't connect

Pidgin trac at pidgin.im
Tue Jun 26 23:46:56 EDT 2007


#1410: After upgrading from pidgin-2.0.0beta7.exe -> pidgin-2.0.0.exe can't
connect
------------------------------+---------------------------------------------
  Reporter:  curt1234         |       Owner:  datallah
      Type:  defect           |      Status:  new     
  Priority:  minor            |   Milestone:  2.1.2   
 Component:  winpidgin (gtk)  |     Version:  2.0.1   
Resolution:                   |    Keywords:          
   Pending:  0                |  
------------------------------+---------------------------------------------
Comment (by rebeca):

 I was having a similar problem to this one with AIM. (My other accounts
 worked fine.)

 I had recently enabled UPnP in my router, and everything worked fine. I
 was able to use AIM normally until someone sent me a file. After receiving
 the file, pidgin crashed and I wasn't able to log into AIM again. At
 first, I thought it might have been a problem with AIM/AOL itself, so I
 logged in through the AIM client and everything was worked. So, I
 uninstalled pidgin, deleted the .purple folder, re-installed pidgin,
 disabled the firewall, and tried the newest version as well as the older
 ones and the problem continued. Then, I disabled UPnP and AIM started
 working again.

 Why did having UPnP enabled affected pidgin only after I received a file?
 Should I dismiss this as a mere router issue? Any ideas?

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1410#comment:9>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list