Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 69979 - Gaim screennames not showing up
Gaim screennames not showing up
Product: Red Hat Public Beta
Classification: Retired
Component: gaim (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Blizzard
Depends On:
  Show dependency treegraph
Reported: 2002-07-27 13:34 EDT by Rob Murphy
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-27 14:39:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rob Murphy 2002-07-27 13:34:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020712

Description of problem:
When I send or recieve a message using gaim .59, neither screennames nor
timestamps appear to the left of the message sent or received.  In addition,
certain peoples messages cannot be seen at all... all that appears is a newline.

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

How reproducible:

Steps to Reproduce:
1.Start Gaim
2.Send/Receive a message to someone.


Additional info:
Comment 1 Rob Murphy 2002-07-27 13:52:32 EDT
Little update: While I can't see screen names for anyone in a conversation
window, it seems that the messages getting blanked out are from AOL users only,
not AIM/GAIM users.  Hmmm... is this a bug or a feature?
Comment 2 Rob Murphy 2002-07-27 14:39:24 EDT
OK, I got to the bottom of it.. I installed the 75dpi and 100dpi fonts, which
were not installed with a default workstation.  However, you might consider
creating a dependancy, considering gaim was rather unusable without it.
Comment 3 Christopher Blizzard 2002-07-27 18:40:30 EDT
It's been fixed in the tree.

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