Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 77384 - Can't receive text from AOL 8.0 users
Summary: Can't receive text from AOL 8.0 users
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gaim
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-06 05:16 UTC by Ed Weinberg
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-06 15:38:57 UTC

Attachments (Terms of Use)

Description Ed Weinberg 2002-11-06 05:16:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When chatting with AOL 8 users I can't see their text.  They can see my text.  I
can see their emotocons :-), though.

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

How reproducible:

Steps to Reproduce:
1.start gaim on a friend who is using aol 8.0
3.verify that you cannot see his text.

Actual Results:  I could not see the AOL 8.0 user's text.

Expected Results:  I should have seen text typed by aol 8.0 user

Additional info:
My fix...
1) download
2) (as root) rpmbuild --rebuild gaim-0.60cvs-1.src.rpm
3) rpm -Uvh /usr/src/redhat/RPMS/i386/gaim-0.60cvs-1.i386.rpm
4) fixed link...the new gaim is in /usr/bin...I think RH puts it in /usr/lib.

Comment 1 Christopher Blizzard 2002-11-06 15:38:49 UTC
In preferences if you click the checkbox that says "Ignore Font Faces" in the
Conversations pane, does this problem go away?

Comment 2 Christopher Blizzard 2002-11-11 19:01:43 UTC
This should have been fixed in rawhide.  Based on the lack of feedback I'm
assuming this was the same problem.

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