Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#19383 closed defect (worksforme)

xpdf is not working under 10.4.11

Reported by: MartinBuchmann (Martin Buchmann) Owned by: ghosthound
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc:
Port: xpdf

Description

Hi,

since a few weeks I only get this error if I try to invoke xpdf

Error: No paper information available - using defaults
Error: No display font for 'Courier'
Error: No display font for 'Courier-Bold'
Error: No display font for 'Courier-BoldOblique'
Error: No display font for 'Courier-Oblique'
Error: No display font for 'Helvetica'
Error: No display font for 'Helvetica-Bold'
Error: No display font for 'Helvetica-BoldOblique'
Error: No display font for 'Helvetica-Oblique'
Error: No display font for 'Symbol'
Error: No display font for 'Times-Bold'
Error: No display font for 'Times-BoldItalic'
Error: No display font for 'Times-Italic'
Error: No display font for 'Times-Roman'
Error: No display font for 'ZapfDingbats'
Warning: Widget must be a VendorShell.
Error: attempt to add non-widget child "dsm" to parent "xpdf" which supports only widgets

I reinstalled openmotif, poppler and xpdf without any change.

I have not found anything in the others tickets. It used to work and I am not aware of any change, unfortunately.

Any hints?

Martin

Change History (13)

comment:1 Changed 16 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to ricci@…

This looks just like #18181, but it's marked as fixed.

comment:2 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:3 Changed 15 years ago by numaryu

I've been having the same problem as the last error message,

Error: attempt to add non-widget child "dsm" to parent "*" which supports only widgets

for xdvi in tex/pTeX. This is a problem of openmotif as described in #18181. All demo programs in /opt/local/share/Xm provided by openmotif give the same error. The solution in #18181 seems not applicable to 10.4.11.

comment:4 in reply to:  3 Changed 15 years ago by ghosthound

Replying to ryusuke.numata@…:

I've been having the same problem as the last error message,

Error: attempt to add non-widget child "dsm" to parent "*" which supports only widgets

for xdvi in tex/pTeX. This is a problem of openmotif as described in #18181. All demo programs in /opt/local/share/Xm provided by openmotif give the same error. The solution in #18181 seems not applicable to 10.4.11.

This sounds like its really a problem w/ openmotif. Any reason to not change it to an openmotif bug (instead of xpdf)?

comment:5 Changed 15 years ago by s.choi@…

Although this ticket was opened a long time ago, I would like to point out my solution for those who will experience more or less similar problem to this

  • I have come to here through Google search.

Basically, this font rendering error comes with a wrong font pointer in your

"xpdfrc" file.

If you open the file with a text editor (e.g., "vim /opt/local/etc/xpdfrc"), you will see lots of "displayFontT1" and its location. The locations of those font files may differ from system to system. In my case (Mac OS X 10.5.7 and Darwin port 1.7.1, and xpdf version 3.02 Revision 5), the font locations are as follows:

displayFontT1 Times-Roman   /opt/local/share/fonts/urw-fonts/n021003l.pfb
displayFontT1 Times-Italic  /opt/local/share/fonts/urw-fonts/n021023l.pfb
displayFontT1 Times-Bold /opt/local/share/fonts/urw-fonts/n021004l.pfb
displayFontT1 Times-BoldItalic /opt/local/share/fonts/urw-fonts/n021024l.pfb
displayFontT1 Helvetica     /opt/local/share/fonts/urw-fonts/n019003l.pfb
displayFontT1 Helvetica-Oblique /opt/local/share/fonts/urw-fonts/n019023l.pfb
displayFontT1 Helvetica-Bold /opt/local/share/fonts/urw-fonts/n019004l.pfb
displayFontT1 Helvetica-BoldOblique /opt/local/share/fonts/urw-fonts/n019024l.pfb
displayFontT1 Courier /opt/local/share/fonts/urw-fonts/n022003l.pfb
displayFontT1 Courier-Oblique /opt/local/share/fonts/urw-fonts/n022023l.pfb
displayFontT1 Courier-Bold /opt/local/share/fonts/urw-fonts/n022004l.pfb
displayFontT1 Courier-BoldOblique /opt/local/share/fonts/urw-fonts/n022024l.pfb
displayFontT1 Symbol        /opt/local/share/fonts/urw-fonts/s050000l.pfb
displayFontT1 ZapfDingbats  /opt/local/share/fonts/urw-fonts/d050000l.pfb

If you can get it right, then xpdf will not complain about displaying those fonts. Hope this helps.

Finally, this is also explained at the original xpdf homepage - http://www.foolabs.com/xpdf/problems.html .

Cheers, Soo-Hyun

comment:6 Changed 15 years ago by MartinBuchmann (Martin Buchmann)

Soo-Hyun,

thanks for your hint. it seems to work. But still gives the following error

Warning: Widget must be a VendorShell.
Error: attempt to add non-widget child "dsm" to parent "xpdf" which supports only widgets

This is a "bug" in the openmotif port, if I understand https://trac.macports.org/ticket/18181 correctly. But I must admit that I do not understand the solution or current status of this bug. I have installed xorg-libXt @1.0.5_2 (active), xpdf and openmotif built fine under 10.5.7 and MacPorst 1.7.1 all ports are uptodate but I am still not getting it to work :-(

Anyone does? TIA

Martin

comment:7 Changed 15 years ago by MartinBuchmann (Martin Buchmann)

Hi,

since I upgraded to xorg-libXt @1.0.6_0 today xpdf is running fine again. I conside this bug as fixed now.

Best regards

Martin

comment:8 Changed 15 years ago by mf2k (Frank Schima)

Resolution: worksforme
Status: newclosed

comment:9 in reply to:  8 Changed 15 years ago by mzucker (Matt Zucker)

I have this bug as well. Just installed xpdf 3.02_5+with_poppler on Mac OS 10.4.11 and I get this console output:

Error: No paper information available - using defaults
Warning: Widget must be a VendorShell.
Error: attempt to add non-widget child "dsm" to parent "xpdf" which supports only widgets

comment:10 Changed 15 years ago by mf2k (Frank Schima)

Please run the following and let us know if the problem persists:

sudo port selfupdate
sudo port upgrade outdated

comment:11 in reply to:  10 Changed 15 years ago by mzucker (Matt Zucker)

Did that. Problem persists.

comment:12 Changed 15 years ago by mzucker (Matt Zucker)

Still not working. Should I file a new ticket here?

comment:13 in reply to:  12 Changed 15 years ago by mf2k (Frank Schima)

Replying to matt.zucker@…:

Still not working. Should I file a new ticket here?

Yes

Note: See TracTickets for help on using tickets.