Bug 59544

Summary:	Bad fonts.scale file + another startup problem
Product:	[Retired] Red Hat Linux	Reporter:	David L. Parsley <parsley>
Component:	abiword	Assignee:	Bernhard Rosenkraenzer <bero>
Status:	CLOSED RAWHIDE	QA Contact:	Aaron Brown <abrown>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.3	CC:	mharris
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:	2002-03-19 19:25:20 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 David L. Parsley 2002-02-10 02:02:48 UTC

Description of Problem:
This is really two bugs in one report. ;-)  The fonts.scale file in the abiword
fonts directory has blank lines at the end, which buggers mkfontdir.  Once I
removed the blank lines it fixed the font problem, but even then abiword
segfaults on startup. :-(

Comment 1 Bernhard Rosenkraenzer 2002-02-27 11:07:40 UTC

This is because for some reason, xset +fp fails to work even if fonts.scale is fixed: 
 
[root@spock fonts]# xset +fp /usr/share/AbiSuite/fonts 
X Error of failed request:  86 
  Major opcode of failed request:  51 (X_SetFontPath) 
  Serial number of failed request:  8 
  Current serial number in output stream:  10 
 
Might be an X bug after all.

Comment 2 David L. Parsley 2002-02-27 19:01:28 UTC

I d/l'ed the latest Abiword from abisource, and the included fonts.scale had the
same problem.  Once I removed the blank lines, though, I did mkfontdir &
chkfontpath (add abisource fonts) and it started fine.  Still crashed whenever I
closed a window tho.  I'll check this out again on the next beta.

Comment 3 Mike A. Harris 2002-02-28 00:14:24 UTC

If the file contains blank lines, then it is a bad file.  ttmkfdir should
be used to create fonts.scale.

xset +fp will never work in a default Red Hat Linux setup because we use
the xfs fotn server, and xset +fp talks to the X server - which is not
serving any fonts.

The proper way for this to be handled IMHO is for the Abiword package to
install its fonts, and run chkfontpath in it's post install script like all of
our other font packages do, which also then allows the fonts to be used by
other applications.

Comment 4 Jay Turner 2002-03-19 19:25:15 UTC

So, what's the resolution to this?