On 2017-11-03 12:05, Ken Brown wrote:
> On 11/3/2017 9:11 AM, Ken Brown wrote:
>> In the meantime, I have another xpdf problem.  After my update of the
>> ghostscript fonts, I get the following errors when starting xpdf:
>>
>> Config Error: No display font for 'Courier'
>> Config Error: No display font for 'Courier-Bold'
>> Config Error: No display font for 'Courier-BoldOblique'
>> Config Error: No display font for 'Courier-Oblique'
>> Config Error: No display font for 'Helvetica'
>> Config Error: No display font for 'Helvetica-Bold'
>> Config Error: No display font for 'Helvetica-BoldOblique'
>> Config Error: No display font for 'Helvetica-Oblique'
>> Config Error: No display font for 'Symbol'
>> Config Error: No display font for 'Times-Bold'
>> Config Error: No display font for 'Times-BoldItalic'
>> Config Error: No display font for 'Times-Italic'
>> Config Error: No display font for 'Times-Roman'
>> Config Error: No display font for 'ZapfDingbats'
>>
>> Reinstalling the old ghostscript-fonts-std-8.11-1 fixes it.  Copying
>> the files from /usr/share/fonts/urw-base35 to
>> /usr/share/ghostscript/fonts doesn't fix it.
>>
>> Do you happen to know how Fedora handles this?  I didn't see anything
>> obvious in xpdf.spec.
> 
> As a (temporary?) workaround, I've added the *.pfb files from the old
> ghostscript-fonts-std-8.11-1 package to urw-base35-fonts.  If I find out
> that Fedora has a better way of handling it, I can always change this.

This needs to be properly fixed in xpdf itself:

https://bugzilla.redhat.com/show_bug.cgi?id=1509862

The patch I posted there *appears* to work, but hasn't been tested much yet.

-- 
Yaakov