Mozilla 1.3 (11.00) and Acrobat plugin not functioning

[Erwin Mascardo]

We've recently switched our departmental browser from Netscape 4 to Mozilla 1.3. One requirement is that PDFs open in the browser window rather than a separate window, which calls for the Acrobat plugin. However, when you try to open a PDF, the following message pops up on the terminal window and the browser dies (no core file):

/usr/lib/dld.sl: Unresolved symbol: XmProcessTraversal (code)
from /home/scc/ods/Acrobat5/Browsers/hppahpux/nppdf.sl

I've also tried using Acrobat 4's plugin (which worked with Netscape 4), with the same result.

I ran into this problem in testing and configured the browser for deployment to use acroread as a helper application (which worked great), but the users insist on having the PDFs open within the browser. Since this looks like a case of Motif not playing nice, would there be a problem with SHLIB_PATH or something that can be fixed with patching?

[Mike Stroyan · Accepted solution]

This is not a problem of Motif not playing nice.
Mozilla didn't invite Motif over to play at all.
Mozilla is using different, non-Motif, widgets.
Even forcing mozilla to preload libXm does not help. The Acrobat plugin is getting 'clever' and trying to use the Motif widgets that netscape created. Adobe will need to create new version of the plugin. I suppose someone could create a 'shim' plugin that reparents acrobat under a mozilla window. I don't see the appeal.

[Steven E. Protter]

mozilla 1.2 might work better, but I think the previous post is right, this is a problem with acrobat 4.

I notice also your error message is for Acrobat5, but I know that Acrobat 4 was the last Acrobat ported to HP-UX.

Perhaps we need to make sure all of our configuration is consistent.

SEP

[Marc Ahrendt]

i have Mozilla 1.6.0.01 and AcroRead 5.09 on HP-UX 11.11 ...and i have the same exact issue!

i tried using Moz 1.6 with ArcoRead 4.05 and got the same results

...has anyone figured out how to get AcroRead to act as a plugin? please note that i am aware it works as a helper application but that is very annoying to our users since it fires off an extra useless Mozilla window indepenedt of the Adobe AcroRead window launched

[Marc Ahrendt]

forgot to mention that the end-users here will be launching PDFs to view several times from one Mozilla session ...so that is why i need to have AcroRead act as a true plugin as so not to get so many extra windows that come with setting AcroRead up as a helper app

...unless, is there a way to have it be a helper application but without firing off an additional Mozilla window?