Bug 614376

Summary:	gv gives Warning: Missing charsets in String to FontSet conversion
Product:	[Fedora] Fedora	Reporter:	Roderick Johnstone <rmj>
Component:	gv	Assignee:	Orion Poplawski <orion>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	12	CC:	ejsheldrake, orion, pertusus
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-26 15:24:28 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 Roderick Johnstone 2010-07-14 10:13:07 UTC

Description of problem:
The most recent update to gv causes it to issue warnings when its run. it seems to work ok though.
linux> gv <any postscript file>
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-efont-biwidth-medium-r-normal--16-*-*-*-*-*-iso10646-1,-gnu-unifont-medium-r-normal--16-*-*-*-*-*-iso10646-1,-adobe-helvetica-medium-r-normal--14-*-*-*-*-*-*-*,-jis-fixed-medium-r-*--16-*-*-*-*-*-jisx0208.1983-0,-*-*-medium-r-*--16-*-*-*-*-*-*-*,*" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset


Version-Release number of selected component (if applicable):
gv-3.7.1-1.fc12.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. run gv on any or no file
2.
3.
  
Actual results:
Warning messages appear. File is displayed.

Expected results:
No warning messages. File is displayed.

Additional info:
This was already mentioned in BZ #600926, but that was closed as duplicate because it was not the main bug reported.

Comment 1 Edward Sheldrake 2010-10-26 14:38:38 UTC

I think this is due to the lack of an encodings.dir file - bug #634039

Comment 2 Roderick Johnstone 2010-10-26 15:24:28 UTC

Edward: Very many thanks.

The problem was in one of our local font directories. Your mkfontdir command in  bug #634039 fixed it nicely.

Closing this report.