PDA

View Full Version : upgraded seamonkey 1.1.12 not recognizing 1.6.0 java-openjdk-plugin gcjwebplugin.so



pwalden
13th November 2008, 10:29 PM
I upgraded from Fedora 7 to Fedora 9, which upgraded me to seamonkey 1.1.12 (from 10 or 11, I think)

I also changed over from the sun java 1.5 plugin to the new java-openjdk-plugin 1.6.0. However, my standard test applet page (http://www.can-d.net/plus.htm) does not work, it says the java may not be enabled.

Seamonkey does show the gcjwebplugin.so plugin as registered in the
about: plugins (about:plugins) page and yes, Java is enabled in the advanced preferences. The about: plugins (about:plugins) shows:


GCJ Web Browser Plugin (using IcedTea) 1.2

File name: gcjwebplugin.so
The GCJ Web Browser Plugin (using IcedTea) executes Java applets.

MIME Type Description Suffixes Enabled
application/x-java-vm IcedTea class,jar Yes
application/x-java-applet IcedTea class,jar Yes
application/x-java-applet;version=1.1 IcedTea class,jar Yes

...etc


If I fire up firefox, the plugin also shows as registered and the above applet works! I can also fire up the openjdk Java Monitoring & Management Console and everyting looks good.

Running seamonkey from a terminal command line yields no errors to the terminal screen. The Tools > Web Development menu does show the Java console as grayed out. The Error console has no errors related to java.

I have run this by the mozilla newsgroups too, with no good response.

I suspect this may be a gcjwebplugin defect. Anyone else have seamonkey and java-openjdk-plugin working?

Any help would be appreciated.

Philip

JohnVV
13th November 2008, 11:25 PM
did you "upgrade" to 9 from 7 or did you do a fresh install of 9
there have been major changes in java since fedora 7
and upgrading 7 to 9 missing 8 will most likely break something .

pwalden
14th November 2008, 12:17 AM
I went directly from 7 to 9. I removed the Sun java, and installed the java-opensdk and java-open-sdk packages.

Firefox works with the same /usr/lib/mozilla file tree, so I think it may be specific to seamonkey.

pwalden
14th November 2008, 06:19 PM
I also have another box with a new F9 installation (no upgrade). It just had firefox and the gcjwebplugin.so. This combination works with http://www.can-d.net/plus.htm.

I then installed seamonkey on this new F9 instance. Starting seamonkey, the gcjwebplugin.so shows as registered and enabled in about: plugins (about:plugins). A quick check of Edit > Preferences > Advanced also shows that Java is enabled. I also checked the Tools > Web Development > Java Console menu and it is not grayed-out, however in my jubilation I do not actually try to bring up the console. So I try my simple (http://www.can-d.net/plus.htm) test site, this comes up like the other F9 instance with a message that java may be disabled. I go back to look at the Java Console, but the menu item is now grayed-out. I go back and try firefox again, and it is still working with that site

So the upgrade versus fresh install theory is ruled out.

Hlingler
14th November 2008, 07:21 PM
I would suggest that you simply install SUN's java instead: http://www.mjmwired.net/resources/mjm-fedora-f9.html#java

As fate would have it, I just happened to start SeaMonkey last night (I almost never use it), and Java (SUN JRE-1.6.0_10-b33) worked fine - but flash-player was totally borked. I've got an older devel snapshot of SeaMonkey-2.0a1.

V

pwalden
14th November 2008, 07:37 PM
I guess I was hoping to not use the Sun java as I wanted to just use yum, and not muck with Sun's rpm.

Sounds like this is a seamonkey or java-opensdk bug that should be reported?

Hlingler
14th November 2008, 07:41 PM
Sounds like a bug to me - but which one? Anything useful in ~/.xsession-errors? Or: start SeaMonkey from CLI and see if there's any useful messages.

FWIW, I've used SUN's RPMs, and never had much problem - occasionally they're removed by updates, but that can be fixed by simply re-installing them.

V

pwalden
14th November 2008, 08:39 PM
The .xsession-errors file has nothing and cli invoke of seamonkey shows nothing either.

I agree that Sun's rpm has not had problems, but it is more complicated (than yum update) to monitor the Sun site for new versions, download, install, and soft link in the plugin. If they(Sun) made it as easy for Linux as they do for windows users, then my argument would be even weaker (looks like Sun is on the ropes though).

I submit a bug somewhere.

pwalden
16th November 2008, 07:17 PM
https://bugzilla.mozilla.org/show_bug.cgi?id=465044

Hlingler
17th November 2008, 06:35 AM
Thanks for stopping back to post the bug report link.

V