Thank you.

--- On Fri, 6/19/09, Montel Edwards <email address hidden> wrote:

From: Montel Edwards <email address hidden>
Subject: Re: [Bug 389322] Re: Pidgin 2.5.5 will not connect to Yahoo! server.
To: <email address hidden>
Date: Friday, June 19, 2009, 2:24 PM

It somewhat I guess could be a permanent fix, but Pidgin should update this
in the newest release.
On Fri, Jun 19, 2009 at 12:45 PM, clombard <email address hidden> wrote:

> OK...this solution seems to work.
> Is a permanent or temporary fix?
> thank you.
>
>
> --- On Fri, 6/19/09, ipmawan <email address hidden> wrote:
>
> From: ipmawan <email address hidden>
> Subject: [Bug 389322] Re: Pidgin 2.5.5 will not connect to Yahoo! server.
> To: <email address hidden>
> Date: Friday, June 19, 2009, 12:48 PM
>
> Below solution works for me.
>
> http://ubuntuforums.org/showthread.php?t=1191064&page=5 post#47
> maybe this thread will be helpful.
>
> http://forum.ubuntu-vn.org/viewtopic...t=1630&start=0
>
> I've done those steps:
>
> 1. Open file /etc/hosts with gedit:
> sudo gedit /etc/hosts
> 2. Add the following line to the end of hosts:
> 66.163.181.184 scs.msg.yahoo.com
> 3. Save and Close
> 4. Restart Pidgin
> OK
> Last edited by attlinux; 9 Hours Ago at 03:22 AM..
>
> --
> Pidgin 2.5.5 and 2.5.6 will not connect to Yahoo! server.
> https://bugs.launchpad.net/bugs/389322
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> --
> Pidgin 2.5.5 and 2.5.6 will not connect to Yahoo! server.
> https://bugs.launchpad.net/bugs/389322
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pidgin” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: pidgin
>
> Just hangs trying to connect to yahoo.
> all other account types seem to be working fine just not yahoo.
> pidgin 2.5.5
> ====================================
> pidgin debug log :
> (09:19:46) account: Connecting to account MyYahooAccount
> (09:19:46) connection: Connecting. gc = 0x8e3e1c8
> (09:19:46) dns: DNS query for 'scs.msg.yahoo.com' queued
> (09:19:46) dns: DNS child 5936 no longer exists
> (09:19:46) dns: Created new DNS child 6064, there are now 1 children.
> (09:19:46) dns: Successfully sent DNS request to child 6064
> (09:19:48) dns: Got response for 'scs.msg.yahoo.com'
> (09:19:48) dnsquery: IP resolved for scs.msg.yahoo.com
> (09:19:48) proxy: Attempting connection to 76.13.15.32
> (09:19:48) proxy: Connecting to scs.msg.yahoo.com:5050 with no proxy
> (09:19:48) proxy: Connection in progress
> (09:19:49) proxy: Connecting to scs.msg.yahoo.com:5050.
> (09:19:49) yahoo: 96 bytes to read, rxlen is 116
> (09:19:49) yahoo: Yahoo Service: 0x57 Status: 1
> (09:19:49) yahoo: yahoo status: 12
> ====================================
> ping to yahoo server :
>  ping scs.msg.yahoo.com
> PING scs.msg.yahoo.com (76.13.15.36) 56(84) bytes of data.
> 64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=1 ttl=48
> time=638 ms
> 64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=2 ttl=48
> time=628 ms
> 64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=3 ttl=48
> time=659 ms
> 64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=4 ttl=48
> time=817 ms
> 64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=5 ttl=48
> time=659 ms
> ====================================
> netstat :
> tcp 0 0 xxx.xxx.xxx.xxx:49159 76.13.15.32:5050 ESTABLISHED
> tcp 0 0 xxx.xxx.xxx.xxx:52467 68.180.217.8:5050 ESTABLISHED
> ====================================
>
> ProblemType: Bug
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/pidgin
> NonfreeKernelModules: nvidia
> Package: pidgin 1:2.5.5-1ubuntu8.1
> ProcEnviron:
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> SourcePackage: pidgin
> Uname: Linux 2.6.28-13-generic i686
>
>
>


-- 
UbuntuWiki
https://wiki.ubuntu.com/MontelEdwards
LaunchpadProfile
https://launchpad.net/~m.deonte
UbuntuBeginnersTeam

-- 
Pidgin 2.5.5 and 2.5.6 will not connect to Yahoo! server.
https://bugs.launchpad.net/bugs/389322
You received this bug notification because you are a direct subscriber
of a duplicate bug.