203575 - pdf and ps documents on the web show up as empty

Status: RESOLVED EXPIRED

(Core Graveyard :: Plug-ins, defect)

Description

[Per Nystrom]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314

This just started happening recently; prior to last week sometime it worked
fine.  I haven't changed anything intentionally, but clearly something is hosed.

When I try to open a pdf or ps document on the web, acrobat (or gv) will load
and then complain with "There was an error opening this document. No such file
or directory."  This only happens with remote pages; I have tested it with local
files and both plug-ins seem to work fine.

It gets weirder.  I tried the same mozilla installation under a different linux
account with the same links, and pdf and ps documents on the web load fine.  So
in my regular linux account, I moved ~/.mozilla to ~/.mozilla_hosed and tried
again, and once a new profile was created, that worked fine too.

I'm pretty convinced that something in ~/.mozilla got messed up, but I'm at a
loss as to what, where to find it, or how it got messed up in the first place. 
I can use the new profile as a workaround, but then I sacrifice all the password
manager and image blocking data I've accumulated.  Plus, I'd really like to know
how this happened so I can avoid it in the future.


Reproducible: Always

Steps to Reproduce:
Using the messed up profile, it happens every time.  I'm not sure how the
profile got messed up, so I can't say how to reproduce that part of the problem.

Comment 1

[Per Nystrom]

I've narrowed the cause of this down.  On a whim, I blew away the Cache
directory in the messed up profile.  The next time I started mozilla, everything
was back to working the way it's supposed to.  I don't know *which* file in the
Cache directory was causing my grief, but at least I now know it was one of them.

As time permits, I may go back and try removing eache file in there one by one
to see which one was the culprit.  When I find it, I'll upload it.

Comment 2

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

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.

Comment 4

[Serge Laviolette]

Well as far as I am concern this is still happenning to me.
Windows 7 64bits Firefox 5
Tks.