Bug 108920 - Gaim doesn't recognize online status properly and Yahoo plug out-of-date.
Summary: Gaim doesn't recognize online status properly and Yahoo plug out-of-date.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gaim
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-03 11:26 UTC by Ali-Reza Anghaie
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-12-02 21:54:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ali-Reza Anghaie 2003-11-03 11:26:11 UTC
Description of problem(s):

1) I have AIM and Jabber accounts authenticating. When any of them get
disconnected the little window saying you were disconnected pops up,
you lose the contacts, etc. But when you go to the 'accounts' tab it
still shows connected (no, it's not and no, I don't have the
autoreconncet plugin selected). If you try to de-select the account so
you can manually reconnect, gaim crashes.

2) The Yahoo plugin included can't connect, I understand Yahoo went
through changes in the past few months that required some work for
compatible authentications.

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

gaim-0.66-3.0.2

How reproducible:

Always.

Steps to Reproduce:
First problem:
1. Login to an AIM account. Leave it overnight, you'll usually get
disconnected once.
2. Close status window, check the 'accounts' window. It will show
you're logged in.
3. Try to de-select / re-select, *poof*, no more Gaim.

Second problem:
1. Try to authenticate to any Yahoo account, it fails.
  
Actual results:

Crash and bang, fails to login to Yahoo too...

Expected results:


Additional info:

Comment 1 Christopher Blizzard 2003-12-02 21:54:46 UTC
gaim 0.74-5 is in the queue as an errata for FC1.  This is probably
fixed there.


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