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 jens@unfaehig.de 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.

I've seen this too...

Linux only, over to Serge.... This sounds familiar, may be a dup?

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.

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?

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 adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.

me

this should have been put to future

reassign

[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.

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

Carsten, do you see this?

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.