118403 - Using Acrobat plugin (nppdf.so) gives missing-action errors

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: PDF (Adobe), defect, P3)

Description

[Jim Avera]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20020105
BuildID:    2002010506

The following appears on stdout whenever a local .pdf file
is opened in a tab:

Warning: Actions not found: addBookmark, viewBookmark, copy, undefined-key,
find, findAgain, history, loadImages, openURL, mailNew, new, openFile, print,
exit, reload, saveAs, paste, delete, cut, undo, historyItem, back, forward,
abort, PageUp, PageDown
Warning: Actions not found: ManagerGadgetNextTabGroup,
ManagerGadgetPrevTabGroup, DrawingAreaInput, addBookmark, viewBookmark, copy,
undefined-key, find, findAgain, history, loadImages, openURL, mailNew, new,
openFile, print, exit, reload, saveAs, paste, delete, cut, undo, historyItem,
back, forward, abort, PageUp, PageDown
Warning: No action proc named "ManagerGadgetArm" is registered for widget "form"

I don't see these errors when using netscape 4.78 and the same plug-in.

(This was originally reported in bug
http://bugzilla.mozilla.org/show_bug.cgi?id=107705
but I'm opening a new bug as suggested by [e-mail]
because that other bug was about scroll bars disappearing
but these errors occur immediately when a .pdf file is opened)

Reproducible: Always
Steps to Reproduce:
1.Install the adobe pdf plug-in
2.Ctl-Shift-L, enter path to a local .pdf file, 
   and select "Open in new navigator tab"
  (probably the use of tab browsing is not relevant)

Actual Results:  Above error messages appear on the terminal.

Comment 1

[Boris Zbarsky [:bzbarsky]]

I've seen this too...

Comment 2

[Peter Lubczynski]

Linux only, over to Serge....

This sounds familiar, may be a dup?

Comment 3

[serge (gone)]

Yes, this is the known acrobat issue.
Those messages are from acrobat when it fails to find 4.x translations,
which is irrelevant for 6.x browser.
It's definitely easy fix in acrobat code (checking for userAgent string)
than disable acrobat's stdout[err] in  mozilla code.
ccing Liz McQuarrie.

Comment 4

[Shankar Unni]

With 0.9.7, the other problem I see is that in the about:plugins page, I see
application/pdf being claimed as handled by both "plugger" and "nppdf.so". Which
one wins out?

How do you say that you want nppdf.so to pick up application/pdf, while leaving
the rest to "plugger"?  Do you have to change the plugger configuration file itself?

Comment 5

[scottputterman]

Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to [e-mail].  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.

Comment 6

[rubydoo123]

me

Comment 7

[rubydoo123]

this should have been put to future

Comment 8

[rubydoo123]

reassign

Comment 9

[Robert Parenton]

[Triaging - Sorry for the bugspam]

This is still around, although the behavior described in comment #4 no longer
occurs on current trunk builds with Acrobat 5.0.8.

Comment 10

[Wayne Mery (:wsmwk)]

does this still happen with a current version, like acrobat v7?

Comment 11

[Wayne Mery (:wsmwk)]

Carsten, do you see this?

Comment 12

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.