Camino 2.1.3pre won't view PDF documents inline any longer

UNCONFIRMED
Unassigned

Status

Camino Graveyard
Plug-ins
UNCONFIRMED
6 years ago
6 years ago

People

(Reporter: fraicold83, Unassigned)

Tracking

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en; rv:1.9.2.29pre) Gecko/20120525 Camino/2.1.3pre (like Firefox/3.6.29pre)
Build ID: 20120525001903

Steps to reproduce:

Just updated to latest version of Camino, Version 2.1.3pre (1.9.2.29pre 20120525001903).  Using Lion.  I attempted to download and open a PDF document.


Actual results:

Camino was unable to open the PDF document.


Expected results:

Previous Pre version was able to open the PDF documents with no problems.

Comment 1

6 years ago
Any downloaded pdf file or a specific file? If the latter, can you point to the page where the pdf came from ?

Comment 2

6 years ago
Camino has never had the ability to display PDFs, only if you have a PDF plugin. What does "open the PDF" mean? What plugins do you have installed?
(Reporter)

Comment 3

6 years ago
I've been using Camino for over 3 years now.  It has been my favorite Browser due to its simplicity and reliability with Macs.  I've used it with OSX 10.5 and 10.6.  Now with Lion, I started to have problems downloading and viewing PDF documents online.  Let me explain, (the choice of websites is just one example out of many) if you select the first address, you go to the second address which will either open (you can view the PDF document on your browser) or download the PDF document to your computer.  
http://www.classicalguitarschool.net/en/Download.aspx?id=1024
http://www.classicalguitarschool.net/music/1024.pdf

With Lion, I was unable to do so when using Safari, Opera, and Camino.  Chrome was fully functional to download/viewing PDF documents.  Downloading the Schubert plugin solved this issue with Safari and Opera.  This ability was not still an option with Camino. 

Searching the Camino Forum (http://forums.mozillazine.org/viewforum.php?f=12) I came with the option of downloading a test platform which would disable the PDF plugins.  This option (and downloading the previous version of Schubert) was excellent, problems solved.  Life with Camino was good again.  

Today, Version 2.1.3pre (1.9.2.29pre 20120525001903) was available for download, and I did.  But this "upgrade" came with the loss of PDF download/viewing functionality I explained above.

Gentlemen, I am reporting this for I thought the purpose of this test plattform was to gather information about its functionality.  The ability to download and/or view PDF documents online is extremely important for the average user like me.  I can attest that with Lion, Camino is having problems with those features.  And this upgrade still certainly does has the same weakness.

Comment 4

6 years ago
And to be perfectly clear, you have not recently installed or upgraded Adobe Reader to its latest version? In other words, the only PDF plugin you have in 

~/Library/Internet Plug-Ins/   or in
/Library/Internet Plug-Ins/

is the PDF Browser Plugin version 2.3.2 or earlier?
(Reporter)

Comment 5

6 years ago
At this time, I have installed Adobe Reader 10.1.3 and works fine. 
My computer, among other plugins, has the following @~/Library/Internet Plug-Ins/
1. AdobePDFViewer.plugin v10.1.3
2. AdobePDFViewerNPAPI.plugin v10.1.3
3. PDF Browser Plugin.plugin v2.4.4
4. pdfplugin.plugin  Zero Bytes????

However, Adobe was not a factor when downloading/reading PDFs, for it was installed after downloading the Schubert plugin which enabled Safari and Opera to download and read of PDFs in the web. Chrome never had a problem. Camino required the trial version and the previous version of Schubert, as noted in Camino Help Forum,

New, with Camino (Version 2.1.3pre), I had to disable PDF plugin in ABOUT:CONFIG.  Now I can download PDF documents, and only download.  Still, I can not open PDFs in the browser, like I used to.

Glad to help

Comment 6

6 years ago
Yeah, the latest Adobe Reader update takes over all PDF viewing in Camino and breaks everything. This forum thread explains the symptoms and solution:

http://forums.mozillazine.org/viewtopic.php?f=12&t=2459753

You need to throw out *all* of those plugins if you want to be able to view PDFs in Camino; the Schubert version you have is too new (you have to use 2.3.2 or earlier) and the Adobe plugin is exactly what's breaking this.

I'll leave this unresolved for the moment pending Smokey's answer to this question: do we have a bug on blocklisting the latest Adobe stuff? I know we talked about it, but I don't see a bug on it, and if we have one (or make one), this should probably be duped there.
(In reply to Chris Lawson from comment #6)
> I'll leave this unresolved for the moment pending Smokey's answer to this
> question: do we have a bug on blocklisting the latest Adobe stuff? I know we
> talked about it, but I don't see a bug on it, and if we have one (or make
> one), this should probably be duped there.

The Adobe NPAPI plug-in (which is the one Gecko tries to load) has been blocked since the 27 Apr nightlies (bug 747697 in conjunction with fixing bug 667441).  So that shouldn't be the problem here, since fraicold83@aol.com is using today's nightly ("Version 2.1.3pre (1.9.2.29pre 20120525001903)").

(fraicold83@aol.com, what version of Camino were you using before updating to today's nightly?)

The problem here is either a) having too new of a Schubert plug-in (bug 665385) along with 3 other plug-ins that either don't load or don't work or b) some crazy Gecko plug-in choice bug, of which we've heard rumors for some time (although generally speaking, with the current code, I'm pretty sure the last-modified one wins thanks to the Core patch on bug 740620).

So fraicold83@aol.com needs to do the following things:

1) Undo any disabling of the Schubert plug-in done via about:config (mentioned in comment 5)
2) Quit Camino
3) Remove pdfplugin.plugin, which doesn't work in any browser
4) Install v2.3.x of the Schubert plug-in (this can be done in ~/Library/Application Support/Camino/Internet Plug-Ins, and as long as the last-modified timestamp is newer than v2.4.x in ~/Library/Internet Plug-Ins, Camino will use v2.3.x and Safari/Opera will use 2.4.x)
5) Restart Camino

If viewing PDFs doesn't work at that point, quit Camino, delete ~/Library/Application Support/Camino/pluginreg.dat and restart Camino.

If viewing PDFs still doesn't work, we're probably going to need to make a logging build to figure out what plug-in Gecko is trying to use.

If it does work after Step 5, then this is a duplicate of bug 665385.
Summary: Version 2.1.3pre (1.9.2.29pre 20120525001903), unable to open downloaded PDF documents. → Camino 2.1.3pre won't view PDF documents inline any longer
Component: Downloading → Plug-ins
QA Contact: downloading → plugins
(Reporter)

Comment 8

6 years ago
fraicold83@aol.com, what version of Camino were you using before updating to today's nightly?
I was using the previous Nightly Version of Camino.  That version worked fine after along with the previous version of Schubert.
(Reporter)

Comment 9

6 years ago
Recently updated to this Nightly version, Version 2.1.2 (1.9.2.28 20120308211433).  The problems I described in this post which started on 2012-05-25, are repeating again.  The previous Nightly versions were better suited to view/download PDFs.
Glad to help.

Comment 10

6 years ago
As noted in comment 7, you need to remove the Adobe PDF plugin. If that fixes the problem, this is a duplicate. If the steps in comment 7 do NOT work for you, please let us know.
(In reply to fraicold83 from comment #9)
> Recently updated to this Nightly version, Version 2.1.2 (1.9.2.28
> 20120308211433).

Note that this is a release version, and it is older than the nightly versions that you were using before.

> The problems I described in this post which started on
> 2012-05-25, are repeating again.  The previous Nightly versions were better
> suited to view/download PDFs.

This is almost certainly because you've updated to an older version that doesn't have all of the code changes that were included in the previous nightly versions you were using.
(Reporter)

Comment 12

6 years ago
Problem corrected by installing a different Nightly Version.
You need to log in before you can comment on or make changes to this bug.