Camino and .pdf problem

[Uncle Asad]

I'm having the EXACT same problem. I can't download PDFs using Camino on my iMac. I have a MacBook Pro and a Mac Mini both with the same versions of Camino and they work just fine.

[...]

When I click on a link to download a PDF in Camino, I just get a blank white screen.

What PDF plug-in(s) do you have installed in /Library/Internet Plug-Ins and /Users/<your_username>/Library/Internet Plug-Ins?

The symtoms you've described are exactly the symptoms of having the incompatible version 2.4 or higher of the Schubert PDF Browser Plugin present.

To use the Schubert PDF Browser Plugin with Camino, install version 2.3.x in the ~/Library/Application Support/Camino/Internet Plug-Ins folder. Version 2.3.x works with Camino on 10.5 and 10.6; I'm not sure we've heard one way or another from someone on 10.7.

It's possible that the new Adobe PDF plug-in also causes these symtoms, too; we're still trying to figure that out in other posts in this thread.

[Uncle Asad]

It's possible that the new Adobe PDF plug-in also causes these symtoms, too; we're still trying to figure that out in other posts in this thread.

I deleted the file: AdobePDFViewerNPAPI.plugin from /Library/Internet Plug-ins/ and now everything works perfectly!

Thank-you Duelin for your recommendation - it worked! The Apple techs had no clue.

Ah, thanks for confirming that the new Adobe plug-in also causes the same display problems.

If anyone would like to do some additional troubleshooting for us, can you
1) In Camino, set the camino.disabled_plugin_names hidden pref to "Adobe Acrobat NPAPI Plug-in" (no quotes).
2) Quit Camino.
3) Reinstall AdobePDFViewerNPAPI.plugin
4) Launch Camino

Report what happens when trying to view PDFs (particularly if you have *another* PDF plug-in installed, either version 2.3.x of the Schubert PDF Browser Plugin, or possibly the older Adobe PDF plug-in (I don't know what its human-readable name is, but its filename is "AdobePDFViewer.plugin")

Depending on what we find out, we might be able to block this new plug-in automatically (or users might be able to disable it themselves using the hidden pref described above).

[dukeblue002]

I deleted AdobePDFViewerNPAPI.plugin emptied the trash then closed Camino and restarted my Macbook. Still having same problems. That didn't fix it. Then I downloaded the Schubert PDF Browser Plugin with Camino, version 2.3.x in the ~/Library/Application Support/Camino/Internet Plug-Ins folder and that did not work either. I am not a tech person so I am not going to try and do what Uncle Asad said about disabling plug-ins because I don't want to screw things up. There has to be a simple way that a is easy for me to understand about how to fix this.

[phiw13]

@dukeblue002
Quit Camino and delete the pluginreg.dat in your profiel folder: ~/Library/Application Support/Camino/.

[cleanhead]

If anyone would like to do some additional troubleshooting for us, can you
1) In Camino, set the camino.disabled_plugin_names hidden pref to "Adobe Acrobat NPAPI Plug-in" (no quotes).
2) Quit Camino.
3) Reinstall AdobePDFViewerNPAPI.plugin
4) Launch Camino

Report what happens when trying to view PDFs (particularly if you have *another* PDF plug-in installed, either version 2.3.x of the Schubert PDF Browser Plugin, or possibly the older Adobe PDF plug-in (I don't know what its human-readable name is, but its filename is "AdobePDFViewer.plugin")

I can confirm that Camino disables the AdobePDFViewerNPAPI.plugin using that procedure. Pdf files download in Camino and display online in Safari 5.1.5. It does break Firefox 11.0, but who cares? Sorry, I don't have the Schubert plugin. I prefer to download pdfs, then read them in Preview.

[phiw13]

Report what happens when trying to view PDFs (particularly if you have *another* PDF plug-in installed, either version 2.3.x of the Schubert PDF Browser Plugin, or possibly the older Adobe PDF plug-in (I don't know what its human-readable name is, but its filename is "AdobePDFViewer.plugin")

Disabling / blocking the Adobe NPAPI pdf plugin in Camino and then installing the Shubert plugin in ~/Application Support/Camino/Internet plugins allows to view PDF files in the browser without problems (tested on 10.7.3).

[RPMozley]

Just updated Adobe Reader 10.1.3 and new NPAPI plugin installed. I've already got the Shubert plugin installed, and testing with this link to a test pdf I didn't encounter any issue with it not displaying (without having to block the Adobe plugin).

[LarsS]

This thread is really helpful and I had the same problem. Now I got rid of that Adobe plug-in which clearly was installed with the lastest Adobe Reader update. Camino works perfect again.

Thanks!

[Uncle Asad]

Just updated Adobe Reader 10.1.3 and new NPAPI plugin installed. I've already got the Shubert plugin installed, and testing with this link to a test pdf I didn't encounter any issue with it not displaying (without having to block the Adobe plugin).

What's the timestamp on each (the .plugin directory, not any of the contents), and were they both installed in the same folder, or are they in different Internet Plug-Ins folders?

[Uncle Asad]

This thread is really helpful and I had the same problem. Now I got rid of that Adobe plug-in which clearly was installed with the lastest Adobe Reader update. Camino works perfect again.

It's possible Adobe will try to continue to re-install that plug-in, so we're working on a way in Camino to disable it (prevent Gecko from using it). Thanks to everyone who has contributed here!

[RPMozley]

What's the timestamp on each (the .plugin directory, not any of the contents), and were they both installed in the same folder, or are they in different Internet Plug-Ins folders?

The time stamp for the new NPAPI was at install time, as for the other I don't recall at the moment but it certainly wasn't install time (creation or modification - will update post when I find out date).
Both plugins were installed in the all user Library, installer asked for admin password.

[herbs]

Howdy,

I seem to remember that there is a preference in Adobe Reader that controls the installation of the plugins. I've turned that off and AR updates don't try to re-install. The first time around I may have manually removed the plugins.

PS: Don't use the Shubert plugin either. Just download and manually open in Preview.

Good Luck,
Herb Schulz

[LarsS]

This thread is really helpful and I had the same problem. Now I got rid of that Adobe plug-in which clearly was installed with the lastest Adobe Reader update. Camino works perfect again.

It's possible Adobe will try to continue to re-install that plug-in, so we're working on a way in Camino to disable it (prevent Gecko from using it). Thanks to everyone who has contributed here!

That'd be great!

[Uncle Asad]

What's the timestamp on each (the .plugin directory, not any of the contents), and were they both installed in the same folder, or are they in different Internet Plug-Ins folders?

The time stamp for the new NPAPI was at install time, as for the other I don't recall at the moment but it certainly wasn't install time (creation or modification - will update post when I find out date).
Both plugins were installed in the all user Library, installer asked for admin password.

Thanks! Just trying to see if there's something obvious (based on what we know about the mess that is Gecko's "determine which plug-in to use" logic; usually a newer one wins) to explain why you didn't have any problems while everyone else did

[RPMozley]

Ah, well I do have Schubert plugin installed within the Camino profile folder, which does seem to take precedence. Sorry I didn't specify that previously.