Closed Bug 488947 Opened 15 years ago Closed 15 years ago

[REGRESSION] IcedTeaPlugin does not work at all in seamonkey 2.0b1pre

Categories

(Plugins Graveyard :: Java (IcedTea), defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Apr 2010

People

(Reporter: mozilla, Unassigned)

Details

Attachments

(3 files)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; cs; rv:1.9.1b4pre) Gecko/20090417 SeaMonkey/2.0b1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; cs; rv:1.9.1b4pre) Gecko/20090417 SeaMonkey/2.0b1pre

In Seamonkey 2.0a3 and in Firefox 3.0.4, the IcedTeaPlugin (java plugin shipped with openjdk) works just fine. In Seamonkey 2.0b1pre-20090311 and 2.0b1pre-20090417 (and possibly others), it spits two errors very early and does not work at all:
../IcedTeaPlugin.cc:3708: Error: create process
../IcedTeaPlugin.cc:1661: Error: started appletviewer

I'm attaching error outputs with ICEDTEAPLUGIN_DEBUG=1.

Though this may be an error on IcedTeaPlugin's side, I believe it is more of a problem in Seamonkey, since Sun Java plugin stopped working at about the same time (which led me to replacing Sun Java with openjdk, now it at least does not crash/hang :)).

Reproducible: Always

Steps to Reproduce:
1. visit http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/example1.html
Attached file 2.0a3 log
Attached file 2.0b1pre-20090311 log
Attached file 2.0b1pre-20090417 log
Fedora 10.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090418 NOT Firefox/2.0.0.20 SeaMonkey/2.0b1pre ID:20090418123653

Mine stops working too, with these errors on console:
[misak@misak bin]$ ./seamonkey
cz-service: No windows, starting new one.
IcedTeaPlugin.cc:3632: Error: create process
IcedTeaPlugin.cc:1659: Error: started appletviewer

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_write_chars: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3841: Error: Failed to write bytes to output channel

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_flush: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3855: Error: Failed to flush bytes to output channel

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_write_chars: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3841: Error: Failed to write bytes to output channel

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_flush: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3855: Error: Failed to flush bytes to output channel

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_write_chars: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3841: Error: Failed to write bytes to output channel

(seamonkey-bin:21516): GLib-CRITICAL **: g_io_channel_flush: assertion `channel != NULL' failed
IcedTeaPlugin.cc:3855: Error: Failed to flush bytes to output channel

It seems it starts behave this way from last IcedTea update, but i'm not sure.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: General → Plug-ins
Product: SeaMonkey → Core
QA Contact: general → plugins
this may sound like a stupid question, but i'll ask anyway:

why haven't you complained to icedtea?
Because

> Though this may be an error on IcedTeaPlugin's side, I believe it is more of a
> problem in Seamonkey, since Sun Java plugin stopped working at about the same
> time (which led me to replacing Sun Java with openjdk, now it at least does not
> crash/hang :)).

I may file a report there as well if you think that's a good idea.
i do, i do.
fwiw, if i have the right thread, this is probably: http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/8741dfad2f92a59/9a22cfe8766716c0?lnk=gst&q=java+oji#9a22cfe8766716c0

which we announced (m.d.planning is our announce area), assuming it's the right break, this is intentional, and they'll have to fix it.
Ok then.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Component: Plug-ins → Java (IcedTea)
Product: Core → Plugins
QA Contact: plugins → icedtea-java
As stated on the IcedTea bug; you need to upgrade to a newer version of IcedTea6 that includes NPPlugin (the rewrite for the XULRunner 1.9.2+ API).  This can be either 1.7.x (built with the --enable-npplugin option, which is enabled by default if XULRunner 1.9.2 or higher is detected) or 1.8 (which only has this new plugin, the old one having being dropped).
Resolution: WONTFIX → FIXED
Target Milestone: --- → Apr 2010
Version: unspecified → 1.x
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: