Bug 69979 - Gaim screennames not showing up
Summary: Gaim screennames not showing up
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: gaim (Show other bugs)
(Show other bugs)
Version: limbo
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-27 17:34 UTC by Rob Murphy
Modified: 2008-05-01 15:38 UTC (History)
0 users

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


Attachments (Terms of Use)

Description Rob Murphy 2002-07-27 17:34:27 UTC
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:
Always

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

	

Additional info:

Comment 1 Rob Murphy 2002-07-27 17:52:32 UTC
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 18:39:24 UTC
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 22:40:30 UTC
It's been fixed in the tree.


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