Bug 115139
| Summary: | Yahoo no longer connecting? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Fahrlander <brian> |
| Component: | gaim | Assignee: | Christopher Blizzard <blizzard> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | bart.martens, jalrnc, jaredh-1 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-02-12 19:21:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Seth Vidal has published a newer rpm on bug 113264. Does this rpm solve your problem? http://linux.duke.edu/~skvidal/RPMS/fc1/gaim-0.75-0.1.i386.rpm If this solves the problem, then *this* bug should be marked as a duplicate of bug 113264. Nope, sorry....I'm still getting the same thing. "Unable to read". Is there something I can run here to illuninate the problem? strace, tcpdump or something? This may be a duplicate of 114428. Installed gaim-0.75-1.2.0.i386.rpm from updates-testing Yahoo failed to connect -- MSN and AOL both connect fine. Previous version used was gaim-0.74-5.i386.rpm everything worked fine until tonight when MSN started failing to connect. http://download.fedora.us/fedora/fedora/1/i386/RPMS.updates-testing/gaim-0.75-1.2.0.i386.rpm Downgraded to gaim-0.74-5.i386.rpm and everything connected fine including MSN, AIM, and Yahoo Yeah, sorry, guys....I upgraded to gaim-0.75.1.2.0 (as suggested
above) but no effect. I even double-checked the login to make sure it
hadn't changed. Is there some way I can enable the debug and get a
play-by-play? I hate having so little to report, when others are
using this fix with success...
<account>
<protocol>prpl-yahoo</protocol>
<name>WheelDweller</name>
<password>password</password>
<alias>WheelDweller</alias>
<settings>
<setting name='check-mail' type='bool'>0</setting>
<setting name='xfer_port' type='int'>80</setting>
<setting name='server' type='string'>scs.msg.yahoo.com</setting>
<setting name='port' type='int'>5050</setting>
<setting name='xfer_host'
type='string'>filetransfer.msg.yahoo.com</setting>
</settings>
<settings ui='gtk-gaim'>
<setting name='auto-login' type='bool'>1</setting>
</settings>
</account>
This is the detail on the account, though the password is mangled.
Is there anything obvious I'm not seeing?
Thanks
Unfortunately, it's busted until the gaim guys release 0.76. Please see the little message on their home page. Given 0.76 is taking a long time to come out, have you considered applying this patch and releasing it to fedora updates? It works great for me. http://sourceforge.net/tracker/index.php?func=detail&aid=875191&group_id=235&atid=300235 Their cvs also contains the fix to yahoo by the way, but other parts of the application are going through some major work and may be broken. gaim-0.76 with fixed Yahoo is out |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Galeon/1.3.12 Description of problem: Starting a few days ago, the Yahoo account doesn't come up. It delays the appropriate amount of time, and then another window pops up with the helpful statement "WheelDweller has been disconnected. (date and time) Unable to read." Given the changing world of IM protocol, I figure Yahoo has changed again. My password and username still work for logging into the web-side, but that same access pair doesn't work in Gaim. Version-Release number of selected component (if applicable): gaim-0.75-0 How reproducible: Always Steps to Reproduce: 1.Attempt to login with a working Yahoo account. 2.See failure Actual Results: Starting a few days ago, the Yahoo account doesn't come up. It delays the appropriate amount of time, and then another window pops up with the helpful statement "WheelDweller has been disconnected. (date and time) Unable to read." Expected Results: The usual successful login like ICQ, AIM, etc. Additional info: