Hello and thanks for packaging openjdk7!
I'm trying to start tomcat and I get the error,
Caused by: java.io.FileNotFoundException: /usr/lib/x86_64-linux-gnu/libnss3.so
I suppose a different path must be hardcoded or a symbolic link provided?
Alex
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages openjdk-7-jdk depends on:
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libx11-6 2:1.3.3-4 X11 client-side library
ii openjdk-7-jre 7~b147-2.0~pre2-3 OpenJDK Java runtime, using Hotspo
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages openjdk-7-jdk recommends:
ii libxt-dev 1:1.0.7-1 X11 toolkit intrinsics library (de
Versions of packages openjdk-7-jdk suggests:
pn openjdk-7-demo <none> (no description available)
pn openjdk-7-source <none> (no description available)
pn visualvm <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Hi Alessandro,
Le mercredi 10 août 2011 16:06:51, Alessandro Polverini a écrit :
> Hello and thanks for packaging openjdk7!
> I'm trying to start tomcat and I get the error,
> Caused by: java.io.FileNotFoundException:
> /usr/lib/x86_64-linux-gnu/libnss3.so
>
> I suppose a different path must be hardcoded or a symbolic link provided?
>
> Alex
>
> -- System Information:
> Debian Release: 6.0.2
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'testing'),
> (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.38-2-amd64 (SMP w/12 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
>
> Versions of packages openjdk-7-jdk depends on:
> ii libc6 2.11.2-10 Embedded GNU C Library: Shared
> lib ii libx11-6 2:1.3.3-4 X11 client-side library
> ii openjdk-7-jre 7~b147-2.0~pre2-3 OpenJDK Java runtime, using
> Hotspo ii zlib1g 1:1.2.3.4.dfsg-3 compression library -
> runtime
Given your libc6 version, you seems to be running Debian Squeeze (stable).
Generally speaking, we don't provide support for mixed installation with
experimental with stable packages : it won't work.
In this case, you can't use an pre-multiarch [1] libc/libnss package with any
package depending on multiarch support.
You'll have to use a chroot or wait for some backport to squeeze.
[1] http://wiki.debian.org/Multiarch
Cheers,
--
Damien - Debian Developper
http://wiki.debian.org/DamienRaudeMorvan
Hi Damien,
I suppose to reconsider opening this bug again, as it has been fixed in openjk-6 as it can be seen in bug 634058.
With current nss libs, the location of libnss3.so is in fact /usr/lib/x86_64-linux-gnu/libnss3.so. However programs using libsoftokn3.so, which is needed by JCA's PKCS11 class, can't find the library as it is located at /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so.
The bug report suggests changing the nss directory in /etc/java-7-openjdk/security/nss.cfg. By altering it to /usr/lib/x86_64-linux-gnu/nss libsoftokn3.so is found, but libnss3.so is not, as /usr/lib/x86_64-linux-gnu/nss/libnss3.so is the wrong path.
To me it seems the nss lib locations are all correct.
My library versions are:
libnss3-1d 3.12.10-3
libc6 2.13-10
Unaltered nss path leads to:
Caused by: java.security.ProviderException: Library /usr/lib/x86_64-linux-gnu/libsoftokn3.so does not exist
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:292)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103)
Altered nss path:
Caused by: java.io.FileNotFoundException: /usr/lib/x86_64-linux-gnu/nss/libnss3.so
at sun.security.pkcs11.Secmod.initialize(Secmod.java:186)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:206)
... 26 more
I hope this information helps to get some clarity about the problem.
Perhaps the patch that made it work for openjdk-6 6b23~pre4-1 can be applied to openjdk-7 as well.
Best regards
Tobias Wich