When attempting to connect to Yahoo I get an error about "being disconnected" and "incorrect password". This issue does not occur with 0.75-r10. Reproducible: Always Steps to Reproduce: 1. emerge gaim-0.76.ebuild
Can you get the relevant output from gaim -d when you try to connect to just the Yahoo account? Also is this from behind a firewall/proxy that might not be allowing port 5050 though? Try with port 23.
Same here. gaim -d gives: proxy: Connecting to scs.msg.yahoo.com:5050 with no proxy proxy: Connect would have blocked. proxy: Connected. yahoo: 99 bytes to read, rxlen is 119 yahoo: Yahoo Service: 0x57 Status: 1 yahoo: Key: 1 Value: [user-name-here] yahoo: Key: 94 Value: y/8*(z%r*5*e-n&a-k-(h&q%v*r^z^8&w-n/j*d^(v)/e)|3*r*5^y+8+l-k|(v^4)) yahoo: Key: 13 Value: 1 yahoo: 46 bytes to read, rxlen is 66 yahoo: Yahoo Service: 0x54 Status: -1 yahoo: Key: 1 Value: [user-name-here] yahoo: Key: 66 Value: 13 yahoo: Key: 0 Value: [user-name-here]
Where is the bit where you are getting disconnected?
disconnects immediately after. The next lines of output after the posted yahoo: ... ones are: account: Disconnecting account 0x663bd0 connection: Disconnecting connection 0x85a9c0 blist: Destroying connection: Destroying connection 0x85a9c0 accounts: Writing accounts to disk.
Armin did you build with USE="debug"?
remerged with debug, no change.
Just to make sure, since I had a user with this problem contact me: You guys are just using your usernames to login, not 'username@yahoo.com', right? I hate to ask but it came up.
yes, just the username :-) and to have it out of the way, the same username settings worked fine before yahoo got smart and broke things last year (and, for a while, after the initial gaim hack around that).
Alright can you emerge ymessenger and see if that can connect. If it can, the gaim devs ask that you get a packet capture of the connection process and post it here.
Sorry by 'here' I meant post it in a new upstream bug. Be sure to reference new bug URL here and ref this bug URL there.
packet capture post done as new bug 47001
*** Bug 47001 has been marked as a duplicate of this bug. ***
ok, so now what? should I repost anything here or take a hint and stop complaining?
I said new _upstream_ bug, with Gaim's sourceforge.net tracker. What exactly is your capture of? Josh you are on amd64 too?
Can either of you try connecting from gaim 0.76 built on a 32-bit machine?
I'm told from the gaim developers that "the yahoo auth code comes from trillian, where the whole world is 32 bit and little endian, so they can do really stupid things" So I'd like to confirm if it works on 32 bit for you and not 64, then I'll mark it upstream.
Sorry about that - it dawned on me a little after posting that I was probably confused by the emerge warning about only "NOT" reporting bugs with the gaim tracker and I didn't register 'upstream' properly. :-) the capture is of the "YMSG[...]" content of the gaim-yahoo exchanges (ethereal classifies it as ym-type, so that makes it easy). I can get to a 32bit machine, but it's not gentoo and I'll have to compile gaim from the original tarball - if I'm not still too slow this morning, the yahoo plugin is not affected by gentoo patches, right?
yahoo works on a 32-bit machine compiled from the sf.net tarball.
http://sourceforge.net/tracker/index.php?func=detail&aid=931227&group_id=235&atid=100235 Confirmed on many fronts that this is upstream in Yahoo auth shared by Trillian and Gaim.
