Debian Bug report logs - #184666
mozilla: java plugin seems to be broken

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Robert Hart <enxrah@nottingham.ac.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mozilla: java plugin seems to be broken

Date: Fri, 14 Mar 2003 00:42:48 +0000

Package: mozilla
Version: 2:1.2.1-10
Severity: important
Tags: sid

I noticed today that the java plugin seems to have become broken, and
I'm guessing it's something to do with the latest upload of mozilla. 

I had been using the rpm from java.sun.com (via alien), and have had
no problems, however since running into the problem, I have tried the
latest package from java.sun.com, and also from
ftp://ftp.tux.org/pub/java/debian  

Is this related to the compiler change?

I do realise that the java-plugin is not an official part of debian.

Rob

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux euclid 2.5.64 #2 Wed Mar 12 22:27:09 GMT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages mozilla depends on:
ii  mozilla-browser  2:1.2.1-10              Mozilla Web Browser - core and bro
ii  mozilla-browser- 0.0.20030305.09.trunk-1 An Open Source WWW browser for X a
ii  mozilla-mailnews 2:1.2.1-10              Mozilla Web Browser - mail and new
ii  mozilla-psm      2:1.2.1-10              Mozilla Web Browser - Personal Sec

-- no debconf information

Message #10 received at 184666-close@bugs.debian.org (full text, mbox, reply):

From: Takuo KITAME <kitame@northeye.org>

To: Robert Hart <enxrah@nottingham.ac.uk>, 184666-close@bugs.debian.org

Subject: Re: Bug#184666: mozilla: java plugin seems to be broken

Date: 14 Mar 2003 17:30:21 +0900

> Package: mozilla
> Version: 2:1.2.1-10
> Severity: important
> Tags: sid
> 
> I noticed today that the java plugin seems to have become broken, and
> I'm guessing it's something to do with the latest upload of mozilla. 
> 
> I had been using the rpm from java.sun.com (via alien), and have had
> no problems, however since running into the problem, I have tried the
> latest package from java.sun.com, and also from
> ftp://ftp.tux.org/pub/java/debian  
> 
> Is this related to the compiler change?
> 

Yes. Why don't you read the changelog before submit?
This is not mozilla's problem. Plugin should be compiled with gcc-3.2. 

-- 
Takuo KITAME.

Message #15 received at 184666@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@excelhustler.com>

To: 184666@bugs.debian.org, 184666-submitter@bugs.debian.org, mozilla@packages.debian.org

Subject: And...?

Date: Fri, 14 Mar 2003 15:12:39 -0600

Shouldn't this be reassigned to the appropriate package, or at least point
the submitter to the new info?

-- John

Message #23 received at 184666@bugs.debian.org (full text, mbox, reply):

From: Kaz Sasayama <kaz2003@hypercore.co.jp>

To: 184666@bugs.debian.org

Subject: How can we request commercial plugin developers to compile their plugin with gcc-3.2?

Date: Sun, 16 Mar 2003 11:48:32 +0900

Then, how can we request commercial plugin developers to compile their
plugin with gcc-3.2 before Mozilla's default compiler (for binary
distribution) changes? As you know, the world is not Debian-centric yet!

Note that since Mozilla's plugin scriptability is now XPCOM-based, the
C++ ABI change will affect all scriptable plugins too.

-- 
Kaz Sasayama <kaz2003@hypercore.co.jp>; Screen Name: kazssym
Hypercore <http://www.hypercore.co.jp/> for Open-Source software.

Message #28 received at 184666@bugs.debian.org (full text, mbox, reply):

From: Kaz Sasayama <kaz2003@hypercore.co.jp>

To: 184666@bugs.debian.org

Subject: Blackdown Java compiled by GCC 3.2.1 now available

Date: Sun, 16 Mar 2003 14:27:38 +0900

According to the following page, there is a version of Java (including
plugin) compiled by GCC 3.2.1 available now:

http://www.blackdown.org/java-linux/java2-status/jdk1.4-status.html


This should be documented, especially in README.Debian.

-- 
Kaz Sasayama <kaz2003@hypercore.co.jp>; Screen Name: kazssym
Hypercore <http://www.hypercore.co.jp/> for Open-Source software.

Message #33 received at 184666@bugs.debian.org (full text, mbox, reply):

From: Steffen Burmeister <der@dolph.de>

To: 184666@bugs.debian.org

Subject: Re: Blackdown Java compiled by GCC 3.2.1 now available

Date: Sat, 12 Apr 2003 08:57:31 +0200

[Message part 1 (text/plain, inline)]

Yes, the versions compiled with gcc 3.2 do work in sid. You
can get them here:
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.4.1/i386/01

The debian packages for sid provided by blackdown are out of
date however. So for now you have to install the jdk/jre
manually. I just filed a bug-report at blackdown, so perhaps
the deb's will get updated.

Cheers

  Dolph

-- 
 Steffen Burmeister, Dipl. Wirtschaftsinformatiker (BA)
 mailto:der@dolph.de       http://www.dolph.de
 PGP Key-id: 0x882E5FA7    Key: http://www.dolph.de/pgp_pub_key.asc 

[Message part 2 (application/pgp-signature, inline)]

Message #38 received at 184666@bugs.debian.org (full text, mbox, reply):

From: Jens Müller <jens.mueller@ira.uka.de>

To: 184666@bugs.debian.org

Cc: Steffen Burmeister <der@dolph.de>

Subject: URL?

Date: Fri, 02 May 2003 21:37:16 +0200

Dolph, does that bug report have a URL?

Jens

Message #43 received at 184666@bugs.debian.org (full text, mbox, reply):

From: Steffen Burmeister <der@dolph.de>

To: Jens M?ller <jens.mueller@ira.uka.de>

Cc: 184666@bugs.debian.org

Subject: Re: URL?

Date: Sat, 3 May 2003 13:24:42 +0200

[Message part 1 (text/plain, inline)]

Hi Jens,

> Dolph, does that bug report have a URL?

Sure. Sorry I've forgotten to report it. Unfortuntately the
bug is still in incoming at blackdown. But take a Look by
yourself ;-)

http://www.blackdown.org/cgi-bin/jdk/incoming?id=2828;user=guest;selectid=2828


  Dolph

-- 
 Steffen Burmeister, Dipl. Wirtschaftsinformatiker (BA)
 mailto:der@dolph.de       http://www.dolph.de
 PGP Key-id: 0x882E5FA7    Key: http://www.dolph.de/pgp_pub_key.asc 

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.