Bug 13303

Summary:	Installing XFree86-75dpi-fonts doesn't add them to font path
Product:	[Retired] Red Hat Linux	Reporter:	Nitin Dahyabhai <nitind>
Component:	XFree86	Assignee:	Preston Brown <pbrown>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	katzj, notting
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-07-03 05:19:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nitin Dahyabhai 2000-07-01 00:19:27 UTC

Installed a GNOME Workstation, but the 75dpi font directory
was never added to the font path.  All of the window titles
and dialog box text were displayed using a monospaced font
until I added the path; then the Helvetica font was used
[as it should have been].

A query of the installed package shows that there are no
(un)install scripts, unlike in Zoot and Beta 2's
XFree86-ISO8859-9-75dpi-fonts.

Comment 1 Jeremy Katz 2000-07-02 05:10:58 UTC

This appears to be a general problem with the font packages, as the 100dpi fonts
were also not added to my fontpath, even though I installed them

Comment 2 Bill Nottingham 2000-07-03 05:09:52 UTC

Does this still happen with the 0.29 packages?

Comment 3 Jeremy Katz 2000-07-03 05:19:02 UTC

I did an upgrade to the 0.29 packages last night in a batch on my laptop and the
path for the 75 and 100 dpi fonts didn't get added.   But, I just updated to the
0.29 packages on my desktop (though remotely and I just did the font packages by
themselves) and it worked fine and an xfs upgrade then made the xfs package
config file a .rpmnew as it is %config(noreplace).   So inconclusive would be my
answer there I guess }=\

Comment 4 Bill Nottingham 2000-07-03 05:27:21 UTC

The font packages didn't prereq chkfontpath, which could cause strange
behavior. This will be fixed in 0.30 and later; if the problem persists,
please re-open.