For a couple of weeks (or months?) now, Camino (1.5) and Firefox (2.0.0.4) no longer recognize the plug-in. Even basic pages show 'Click here to get plugin' and broken link/plugin symbol (Camino) or simply omit any content created by Java.
The packages of both Camino and Firefox contain the plug-in, I've just installed 0.9.6.3, deleted the ones in the browser packages, touched the MRJ, restarted the browsers, no change.
Java works fine in Safari. It reads: 1.5.0_07 on the Java test page. MBP Core 2 Duo, 10.4.10 (all latest patches).
Any ideas.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The plugin works fine for me, just tested it in Seamonkey and a recent NB of Camino (2007071104 (1.6a1pre)). I'm still in a PPC environment, tho' so it's prolly not a real comparison.
Have you rebooted lately? Might be worth a shot. Or have you installed the said-to-be problematic QuickTime 7.2 update? Maybe that's hosing things up. How about the freshness of the other browser plugins?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oops, I just re-read your post, and saw that this has been going on for a while. So QT is prolly not a factor. My guess is that something is hosed in your system. I would try re-installing 10.4.10, using the combo updater, and see if that cleans things up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Make sure you've installed both parts of the Java Embedding Plugin
(JavaEmbeddingPlugin.bundle and MRJPlugin.plugin) in /Library/Internet
Plug-Ins/ and that both come from the same JEP version. Also
double-check to make sure you've really cleared out your browser's
Contents/MacOS/plugins directory.
What shows up in your list of plugins when you do about:plugins?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your suggestions. Firefox had Java disabled, enabling it fixed it there. So it seems to be a Camino problem. (I never use Firefox, only for testing purposes, I should have checked its settings properly.)
Camino 1.5 has an "Enable plug-ins" setting. Make sure this is
checked -- if it isn't Java will also be disabled.
But if your "Enable plug-ins" setting is already checked, I suspect
the problem is a setting that's only accessible via about:config.
A quick way to test this is to (temporarily) give Camino a "clean
profile":
1. Quit Camino
2. Rename the Camino directory in ~/Library/Application Support/ (the
Library/Application Support/Camino directory under your home
directory) to something like Camino.bak.
3. Start Camino.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Enable Plug-ins" was checked. Creating a clean profile for Camino did not fix it. Creating a new user on the OS level fixed it. This seems as much a Camino problem as a Java plug-in problem and even more a specific conflict of my user set-up.
Are there any other user specific Camino settings outside of the Camino folder in Application Support? Conflicts with other plugins? I've ran DiskWarrior and cleaned all possible caches with Onyx. I guess I otherwise have to use the tedious approach of moving stuff over one by one to the new user and see when (if at all) Java in Camino breaks there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Are there any other user specific Camino settings outside of the
> Camino folder in Application Support?
There are also Camino directories in ~/Library/Caches and
~/Library/Caches/Metadata, and there's an org.mozilla.camino.plist
file in ~/Library/Preferences (which you can read by doing 'defaults
org.mozilla.camino' at a Terminal prompt). But none of these are
likely to be causing your problem.
> Conflicts with other plugins?
None that I'm aware of ... though you may eventually be able to tell
me otherwise.
> I guess I otherwise have to use the tedious approach of moving stuff
> over one by one to the new user and see when (if at all) Java in
> Camino breaks there.
I'm afraid so. Let me know if you find anything interesting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For a couple of weeks (or months?) now, Camino (1.5) and Firefox (2.0.0.4) no longer recognize the plug-in. Even basic pages show 'Click here to get plugin' and broken link/plugin symbol (Camino) or simply omit any content created by Java.
http://www.java.com/en/download/help/testvm.xml
in Firefox states "Java Runtime Environment is not working on your system", Camino shows the broken plugin symbol.
The packages of both Camino and Firefox contain the plug-in, I've just installed 0.9.6.3, deleted the ones in the browser packages, touched the MRJ, restarted the browsers, no change.
Java works fine in Safari. It reads: 1.5.0_07 on the Java test page. MBP Core 2 Duo, 10.4.10 (all latest patches).
Any ideas.
The plugin works fine for me, just tested it in Seamonkey and a recent NB of Camino (2007071104 (1.6a1pre)). I'm still in a PPC environment, tho' so it's prolly not a real comparison.
Have you rebooted lately? Might be worth a shot. Or have you installed the said-to-be problematic QuickTime 7.2 update? Maybe that's hosing things up. How about the freshness of the other browser plugins?
Oops, I just re-read your post, and saw that this has been going on for a while. So QT is prolly not a factor. My guess is that something is hosed in your system. I would try re-installing 10.4.10, using the combo updater, and see if that cleans things up.
I can't guess what the problem might be.
Make sure you've installed both parts of the Java Embedding Plugin
(JavaEmbeddingPlugin.bundle and MRJPlugin.plugin) in /Library/Internet
Plug-Ins/ and that both come from the same JEP version. Also
double-check to make sure you've really cleared out your browser's
Contents/MacOS/plugins directory.
What shows up in your list of plugins when you do about:plugins?
One more thing -- make sure you haven't disabled Java.
> make sure you've really cleared out your browser's
> Contents/MacOS/plugins directory.
Don't (of course) completely empty this directory. Just make sure it
doesn't contain either MRJPlugin.plugin or JavaEmbeddingPlugin.bundle.
Thanks for your suggestions. Firefox had Java disabled, enabling it fixed it there. So it seems to be a Camino problem. (I never use Firefox, only for testing purposes, I should have checked its settings properly.)
In Camino 1.5 about:plugins shows the following:
http://homepage.hispeed.ch/kukushka/About-Plugins.html
What this html file does not show is broken plugin symbol highlighted here in this screenshot:
http://homepage.hispeed.ch/kukushka/about-plugins-screenshot.png
Camino 1.5 has an "Enable plug-ins" setting. Make sure this is
checked -- if it isn't Java will also be disabled.
But if your "Enable plug-ins" setting is already checked, I suspect
the problem is a setting that's only accessible via about:config.
A quick way to test this is to (temporarily) give Camino a "clean
profile":
1. Quit Camino
2. Rename the Camino directory in ~/Library/Application Support/ (the
Library/Application Support/Camino directory under your home
directory) to something like Camino.bak.
3. Start Camino.
"Enable Plug-ins" was checked. Creating a clean profile for Camino did not fix it. Creating a new user on the OS level fixed it. This seems as much a Camino problem as a Java plug-in problem and even more a specific conflict of my user set-up.
Are there any other user specific Camino settings outside of the Camino folder in Application Support? Conflicts with other plugins? I've ran DiskWarrior and cleaned all possible caches with Onyx. I guess I otherwise have to use the tedious approach of moving stuff over one by one to the new user and see when (if at all) Java in Camino breaks there.
> Are there any other user specific Camino settings outside of the
> Camino folder in Application Support?
There are also Camino directories in ~/Library/Caches and
~/Library/Caches/Metadata, and there's an org.mozilla.camino.plist
file in ~/Library/Preferences (which you can read by doing 'defaults
org.mozilla.camino' at a Terminal prompt). But none of these are
likely to be causing your problem.
> Conflicts with other plugins?
None that I'm aware of ... though you may eventually be able to tell
me otherwise.
> I guess I otherwise have to use the tedious approach of moving stuff
> over one by one to the new user and see when (if at all) Java in
> Camino breaks there.
I'm afraid so. Let me know if you find anything interesting.
> 'defaults org.mozilla.camino'
Oops, that should have been 'defaults read org.mozilla.camino'.