Bug 19731 – xterm in XFree86-4.0.1-1 has font problems

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 19731 - xterm in XFree86-4.0.1-1 has font problems

Summary:	xterm in XFree86-4.0.1-1 has font problems

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	XFree86 (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mike A. Harris
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-10-24 21:35 EDT by dh_redhat
Modified:	2007-04-18 12:29 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-31 14:00:50 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description dh_redhat 2000-10-24 21:35:20 EDT

When using the 'fixed' font with xterm, the bold version of it is
unreadable.
Note that the same font setting (fixed, bold) in rxvt or gnome-terminal
looks correct.

Comment 1 Mike A. Harris 2001-03-31 10:19:36 EST

Hmm.  Seems to look ok on my machine..  perhaps I'm not set up the same tho..

Can you provide me with the exact steps to duplicate the problem?

Comment 2 dh_redhat 2001-03-31 14:00:46 EST

I run 'xterm -fn fixed', my shell is 'zsh' with the prompt set as PS1='%B%n%b@%m
(%B%~%b%)%!%# ' The bold part of the prompt is unreadable when using xterm, but 
it is fine with rxvt.

Comment 3 Mike A. Harris 2001-10-31 22:14:10 EST

I consider this a configuration problem rather than a bug.  If you
play around with font settings, you should be able to get it to
display.

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