Hi All-

I'm evidently experiencing a bug in the (masked) acroread-7.0 package. I'd
like to help out and find a solution, but I'm not sure where to start...

The bug is with acroread's interaction with mozilla-firefox. Before
installing acroread, Firefox would download and view (in gpdf) any PDF
file that was clicked from a hyperlink in a browser window. After
installing acroread, Firefox worked (including launching acroread instead
of gpdf) until all windows were closed.

After starting a new Firefox session, Firefox no longer successfully
launched a PDF reader. Regardless of the mimetype settings for
"application/pdf" (configured via the Mimetype Editor 0.2 Firefox
extension) Firefox persisted in freezing immediately after a PDF hyperlink
was clicked. One processor in my dual-processor system was pushed to about
50% consistent load until Firefox was killed, either by Gnome's "force
quit" mechanism or an explicit `killall firefox-bin`.

Tried re-emerging Firefox with no change in behavior.

Behavior returns to normal after `emerge -C acroread`.

I'd like to learn more about the process for dealing with things like
this. Should this be reported as a bug? Has it already been reported as a
bug? If it ends up reported as a bug, how does it get repaired? All of
these areas are new to me but I'd like to learn more...

I see bug #87679, which is the sole hit when searching bugs.gentoo.org for
"ALL firefox acroread" - but this doesn't look like exactly the same
problem since I see no mention of freezing.

Dave

--
[email protected] mailing list

Reply via email to