https://bugzilla.novell.com/show_bug.cgi?id=483018
User mvyskocil@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=483018#c1
Michal Vyskocil changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|NEW |NEEDINFO
CC| |mvyskocil@novell.com
Info Provider| |suse-beta@cboltz.de
Severity|Normal |Major
--- Comment #1 from Michal Vyskocil 2009-03-09 02:38:35 MST ---
Hi,
can you check a legacy Java plugin? Just backup a symlink
/usr/lib/browser-plugins/javaplugin.so and create a new one
ln -sf
/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/plugin/i386/ns7/libjavaplugin_oji.so
And recheck it? The 'Could not initialize class javax.crypto.SunJCE_b' seems to
me as a regression of Sun's bug 6567947 [1], which is an upstream issue.
And about testing. I'm not against it, I can use a opensuse-java ML to announce
of upcoming Sun Java update and packages are exposed via update-test repository
[1] before official update. So you can use an existing infrastructure for
testing of updates and contact me via opensuse-java ML, or via IRC (i'm on
several IRC channels like #opensuse-factory, #suse, #opensuse-buildservice,
..), or via bugzilla.
But there are many specifics with a Sun Java. First of all, it's a third party
package and should be fixed by Sun only. That means we can fill a bug into
bugs.sun.com. But this cannot prevent us to release an update, because it
contains a security fixes (and when we will wait on a bug-free edition, we
should wait forever ;-)).
[1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6567947
[2] http://download.opensuse.org/update/11.1-test/
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.