Red Hat Bugzilla – Bug 155020
acroread 7.0 displays blank when "swallow"ed
Last modified: 2018-04-11 07:53:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Galeon/1.3.20
Description of problem:
The acrobat reader 7.0 i386.rpm released by Adobe contains the /usr/bin/acroread executable, but does not activate its own mozilla plugin by default.
The shipped /etc/mozpluggerrc lists acroread ahead of xpdf and will execute it with the +useFrontEndProgram option for "don't open in existing instance" behavior, but the name of this option has been changed to -openInNewWindow in acoread 7.0, thus causing acroread to exit.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install Adobe acrobat reader 7.0 rpm
2. view URL pointing to PDF file
Actual Results: mozilla shows a blank page
Expected Results: Successful display of PDF file
I suggest trying acroread as a last resort for PDF in /etc/mozpluggerrc, favoring opensource viewers instead. If it is still desirable to support acoread in mozplugger then we should handle the version difference.
Created attachment 113248 [details]
handle acroread 5.x and 7.x difference in options and WM_CLASS
This patch still leaves acroread first in the list.
*** Bug 155018 has been marked as a duplicate of this bug. ***
*** Bug 155019 has been marked as a duplicate of this bug. ***
Me too, works in firefox for me. Plugin works in Mozilla 1.6 FC1
Created attachment 118113 [details]
updated patch to mozplugger-1.7.1-4
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Reporter, could you confirm please, that this bug still could be reproduced with
the updated release of the supported version of Fedora (FC5, FC6, or F7)?
If yes, please, reopen this bug with additional information how it is possible
to reproduce this bug.
In meantime, I have to close this bug as CANTFIX, because it is reported against
not longer supported distribution.
Thanks in advance.