Red Hat Bugzilla – Bug 125162
Empty Fontmap file in ghostscript
Last modified: 2007-11-30 17:10:44 EST
Description of problem:
ghostview is failing when trying to find fonts in a wrong location
due to the empty Fontmap file distributed within the package.
Version-Release number of selected component (if applicable):
Just print to file in OpenOffice using any valid postscript driver
and try to see the PS file with ghostscript.
Steps to Reproduce:
1. Configure a postscript printer in OpenOffice
2. Print any document to a file
3. Try to open it with ghostscript (or try to convert it to pdf).
The postscript file is valid (I think), but ghostview can't find the
fonts correctly and fails to display it (displays blank pages).
The psotscript file should be read correctly... :)
The problem was solved by doing what I read in this post:
I think the ghostscript package should be revised. I'm Cc'ing this
message to the packager of ghostscript.
$ cat Fontmap
% See Fontmap.GS for the syntax of real Fontmap files.
So Fontmap delegates to Fontmap.GS anyway.
You probably modified Fontmap in the first place, and since that file
is marked as %config the new package will have created a
Fontmap.rpmnew. Just mv Fontmap.rpmnew Fontmap.
There was no Fontmap.rpmnew file, just an empty (0 bytes) Fontmap.
Deleting both files (Fontmap and Fontmap.GS), and forcing reinstall of
ghoscript seems to work. I should have seen the contents of Fontmap
before overwriting it the first time.
Nevertheless, more people had the same problem. I made a complete
install of RedHat 9, keeping only my /home partition. Since then, FC1
and FC2 where upgrades from the privious. It's strange I didn't
noticed this problem before... and I don't remember to have changed
this file by hand...
Okay, the crucial information was that this was an upgrade. Something
to look into then.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.