Mozilla 1.5 freezes after PDF displays



14 years ago
12 years ago


(Reporter: paul bateson, Unassigned)



Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.5) Gecko/20031007

I see the other associated bug reports but nothing for Linux. Here it is. I
click on THIS PARTICULAR link and open acroread. acroread functions normally but
I have lost all Mozilla functionality. I have to kill Mozilla to continue.

I have loaded other PDF files with no problem with Mozilla 1.5 and my current
acroread. This is not a consistent problem with PDF files.

Reproducible: Always

Steps to Reproduce:
1. go to web site
2. click on OMERS Update link
3. acroread opens (it is my file association)
3. kill Mozilla 1.5
Actual Results:  
Mozilla 1.5 was killed. Reload and continue. Otherwise no crashing. Good app!

Expected Results:  
From the foregoing Mozilla must realise that I am not techie enough to answer
this question other than acroread should fade away into the sunset and Mozilla
goes onto the next page.

Comment 1

14 years ago
WFM LInux 2004012207 Acrobat Reader 5.0.8 also the plugin is WFM

Comment 2

14 years ago
are you using acroread as a helper app or as a plugin (
Keywords: hang

Comment 3

14 years ago
Good Day...

I searched the mozilla directory (/usr/local/mozilla) and did not find
My user mozilla directory did not contain the file.

The other 'helper app' term, I am not familiar with it.

Give me more info and I will assist you.

Comment 4

14 years ago
Helper apps are found in Edit-> Pref.->Nav.->Helper Apps.
If you didn't find the plugin then you are using a helper app.  Also,
about:plugins will tell you what plugins you have installed.  You should try 1.6
or a nightly and see if that works.
Product: Browser → Seamonkey

Comment 5

13 years ago
is this still a problem with a recent build (1.7 or 1.8b)?  Adobe also released
Reader 7.0 for linux.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.