I have set up an account at Yahoo, but cannot access with Pidgin

Bug #612620 reported by hillhopper
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Pidgin Debug Log : Mon 02 Aug 2010 11:34:35 AM EDT
(11:34:14) util: Writing file prefs.xml to directory /home/hillhopper/.purple
(11:34:14) util: Writing file /home/hillhopper/.purple/prefs.xml
(11:34:21) account: Connecting to account <email address hidden>
(11:34:21) connection: Connecting. gc = 0x8541aa8
(11:34:21) dns: DNS query for 'scsa.msg.yahoo.com' queued
(11:34:21) dns: Created new DNS child 28523, there are now 1 children.
(11:34:21) dns: Successfully sent DNS request to child 28523
(11:34:21) dns: Got response for 'scsa.msg.yahoo.com'
(11:34:21) dnsquery: IP resolved for scsa.msg.yahoo.com
(11:34:21) proxy: Attempting connection to 67.195.186.248
(11:34:21) proxy: Connecting to scsa.msg.yahoo.com:5050 with no proxy
(11:34:21) proxy: Connection in progress
(11:34:22) proxy: Connected to scsa.msg.yahoo.com:5050.
(11:34:22) yahoo: 95 bytes to read, rxlen is 115
(11:34:22) yahoo: Yahoo Service: 0x57 Status: 1
(11:34:22) yahoo: Authentication: In yahoo_auth16_stage1
(11:34:22) util: requesting to fetch a URL
(11:34:22) dns: DNS query for 'login.yahoo.com' queued
(11:34:22) dns: Created new DNS child 28525, there are now 1 children.
(11:34:22) dns: Successfully sent DNS request to child 28525
(11:34:22) dns: Got response for 'login.yahoo.com'
(11:34:22) dnsquery: IP resolved for login.yahoo.com
(11:34:22) proxy: Attempting connection to 69.147.112.160
(11:34:22) proxy: Connecting to login.yahoo.com:443 with no proxy
(11:34:22) proxy: Connection in progress
(11:34:22) proxy: Connected to login.yahoo.com:443.
(11:34:23) nss: subject=CN=login.yahoo.com,OU=Yahoo,O=Yahoo! Inc.,L=Santa Clara,ST=California,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(11:34:23) nss: subject=OU=Equifax Secure Certificate Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(11:34:23) certificate/x509/tls_cached: Starting verify for login.yahoo.com
(11:34:23) certificate/x509/tls_cached: Checking for cached cert...
(11:34:23) certificate/x509/tls_cached: ...Found cached cert
(11:34:23) nss/x509: Loading certificate from /home/hillhopper/.purple/certificates/x509/tls_peers/login.yahoo.com
(11:34:23) certificate/x509/tls_cached: Peer cert matched cached
(11:34:23) certificate: Successfully verified certificate for login.yahoo.com
(11:34:23) util: request constructed
(11:34:24) util: Response headers: 'HTTP/1.1 200 OK

Date: Mon, 02 Aug 2010 15:34:09 GMT

Set-Cookie: B=f8ucj0t65dpbh&b=3&s=sm; expires=Tue, 02-Aug-2012 20:00:00 GMT; path=/; domain=.yahoo.com

P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"

Cache-Control: private

Pragma: no-cache

Expires: Thu, 05 Jan 1995 22:00:00 GMT

Connection: close

Transfer-Encoding: chunked

Content-Type: text/html

'
(11:34:24) yahoo: Authentication: In yahoo_auth16_stage1_cb
(11:34:24) util: requesting to fetch a URL
(11:34:24) dns: DNS query for 'login.yahoo.com' queued
(11:34:24) dns: Created new DNS child 28526, there are now 1 children.
(11:34:24) dns: Successfully sent DNS request to child 28526
(11:34:24) dns: Got response for 'login.yahoo.com'
(11:34:24) dnsquery: IP resolved for login.yahoo.com
(11:34:24) proxy: Attempting connection to 69.147.112.160
(11:34:24) proxy: Connecting to login.yahoo.com:443 with no proxy
(11:34:24) proxy: Connection in progress
(11:34:24) proxy: Connected to login.yahoo.com:443.
(11:34:25) nss: subject=CN=login.yahoo.com,OU=Yahoo,O=Yahoo! Inc.,L=Santa Clara,ST=California,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(11:34:25) nss: subject=OU=Equifax Secure Certificate Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(11:34:25) certificate/x509/tls_cached: Starting verify for login.yahoo.com
(11:34:25) certificate/x509/tls_cached: Checking for cached cert...
(11:34:25) certificate/x509/tls_cached: ...Found cached cert
(11:34:25) nss/x509: Loading certificate from /home/hillhopper/.purple/certificates/x509/tls_peers/login.yahoo.com
(11:34:25) certificate/x509/tls_cached: Peer cert matched cached
(11:34:25) certificate: Successfully verified certificate for login.yahoo.com
(11:34:25) util: request constructed
(11:34:26) util: Response headers: 'HTTP/1.1 200 OK

Date: Mon, 02 Aug 2010 15:34:11 GMT

Set-Cookie: B=0kven5d65dpbj&b=3&s=up; expires=Tue, 02-Aug-2012 20:00:00 GMT; path=/; domain=.yahoo.com

Set-Cookie: Y=v=1&n=cpohcnbcpduo5&l=f.l0dbee/o&p=m1d0oq3012000000&r=mu&lg=en-US&intl=us&np=1; path=/; domain=.yahoo.com

Set-Cookie: T=z=zVuVMBzbDWMBtuTjbmnxrUJNjU3MQY2TjYzNzVOTzA3NTA2ND&a=YAE&sk=DAAE/nwlu7/V.6&ks=EAASMFXfvh3yY_z8wSUM._Nmw--~E&d=c2wBTVRJd05nRXhPVEUwTURJNU9EY3dNamN4TXpZeU9BLS0BYQFZQUUBZwFKM0lZM1NGRElHV0dBVVlJSVZZS0VYSEJCQQFvawFaVzAtAXp6AXpWdVZNQmdXQQF0aXABUWYyaGtC; path=/; domain=.yahoo.com

P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"

Cache-Control: private

Pragma: no-cache

Expires: Thu, 05 Jan 1995 22:00:00 GMT

Connection: close

Transfer-Encoding: chunked

Content-Type: text/html

'
(11:34:26) yahoo: Authentication: In yahoo_auth16_stage2
(11:34:26) yahoo: Authentication: In yahoo_auth16_stage3
(11:34:26) yahoo: yahoo status: 0
(11:34:26) util: Writing file accounts.xml to directory /home/hillhopper/.purple
(11:34:26) util: Writing file /home/hillhopper/.purple/accounts.xml
(11:34:26) yahoo: 11 bytes to read, rxlen is 62
(11:34:26) yahoo: Yahoo Service: 0x54 Status: -1
(11:34:26) yahoo: 11 bytes to read, rxlen is 31
(11:34:26) yahoo: Yahoo Service: 0x7d1 Status: -1
(11:34:26) yahoo: Unhandled service 0x7d1
(11:34:26) account: Disconnecting account 0x817ef70
(11:34:26) connection: Disconnecting connection 0x8541aa8
(11:34:26) connection: Destroying connection 0x8541aa8
(11:34:31) util: Writing file accounts.xml to directory /home/hillhopper/.purple
(11:34:31) util: Writing file /home/hillhopper/.purple/accounts.xml

ProblemType: Bug
Architecture: i386
Date: Mon Aug 2 11:34:44 2010
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia hsfengine
Package: pidgin 1:2.4.1-1ubuntu2.9
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.24-19-generic i686

Tags: apport-bug
Revision history for this message
hillhopper (hillhopper) wrote :
Revision history for this message
hillhopper (hillhopper) wrote :

(11:34:26) account: Disconnecting account 0x817ef70
(11:34:26) connection: Disconnecting connection 0x8541aa8
(11:34:26) connection: Destroying connection 0x8541aa8 This seems to be the termination log statement
(11:34:26) yahoo: Unhandled service 0x7d1 This seems to be the reason for termination.

Revision history for this message
Nathan Williams (nathwill-deactivatedaccount-deactivatedaccount) wrote :

Thank you for reporting this bug. I was unable to replicate this issue with my Yahoo! account in pidgin in Ubuntu 10.04 (not perfect parity, clearly). Have you tested whether you can connect to the same Yahoo! account in another IM client (e.g. Empathy)? If not, the issue may be with your Yahoo! account. (i've been IP blocked by Yahoo! before...)

note you may also need to connect to an alternate server if the default (scsa.message.yahoo.com) is inaccessible from your location. One alternate server is: cs217p2.msg.sp1.yahoo.com.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in pidgin (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.