Bug 133068 - can't login to aim after up2date of gaim
Summary: can't login to aim after up2date of gaim
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gaim   
(Show other bugs)
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Daniel Reed
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-21 14:18 UTC by Bryan Che
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-06 22:03:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Bryan Che 2004-09-21 14:18:21 UTC
Description of problem:

I did an up2date of gaim, and now I can't login to aim.  I get the
message: "bryanc5203 has been disconnected.  Incorrect nickname or
password."  I verified that the name and password are correct.  I am
trying to connect using the default settings for the AIM/ICQ protocol.
 This all worked before doing an up2date of gaim.  I tried rolling
back to an earlier version of gaim, but now I get the same error with
that.  I also tried installing gaim 1.0 from gaim.sourceforge.net, but
I get the same error with that as well.  I was logged into aim fine
just before I closed gaim and did an up2date.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Warren Togami 2004-09-26 03:53:26 UTC
Are you using some proxy or socks?

Comment 2 Warren Togami 2004-10-31 09:03:46 UTC
Also try wiping out ~/.gaim and starting with a new profile.  Any
better behavior?

Comment 3 Bryan Che 2004-11-01 22:32:07 UTC
It turns out that the newer versions of gaim dropped the TOC protcol,
which I had been using for logging into AIM, and switched me to use
AIM's own protocol.  However, I am unable to login to AIM using that
protocol for some reason.  Downgrading Gaim and reverting to TOC made
things work again.  So, either adding support for TOC or fixing the
AIM/Oscor protocol would resolve this bug.

Comment 4 Warren Togami 2004-11-01 22:37:04 UTC
Are you behind a pool NAT where every outgoing connection appears to
come from a different IP address by chance?

Is official Windows AIM broken in the same way?

Comment 5 Bryan Che 2004-11-01 22:42:39 UTC
I don't think I'm behind a pool NAT.  I can login to AIM fine with
AOL's own Linux AIM client and also the Windows AIM client.

Comment 7 Daniel Reed 2004-11-01 23:06:47 UTC
I am able to sign on to AIM with both TOC (in naim) and OSCAR (in gaim) from the
Westford (Boston) office.

Comment 8 Daniel Reed 2004-11-06 22:03:28 UTC
I installed gaim-0.82-1-0.RHEL3.ia64 out of 3.0E-errata on diablo.lab.boston and
was able to sign on using the AIM/ICQ (OSCAR) driver. The latest version in
3.0E-errata is a 1.0, so it appears this version may be outdated anyway.

Note You need to log in before you can comment on or make changes to this bug.