Your message dated Wed, 12 Apr 2017 09:18:57 +0000 with message-id <[email protected]> and subject line Bug#858876: fixed in libjna-java 4.2.2-3 has caused the Debian Bug report #858876, regarding libjna-jni: causes NoClassDefFoundError to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 858876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858876 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libjna-jni Version: 4.2.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, netbeans with native look and feel enabled fails to look up libjnidispatch.so: INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl] java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native at com.sun.jna.platform.unix.X11.<clinit>(X11.java:380) at com.sun.jna.platform.WindowUtils$X11WindowUtils.getAlphaVisualIDs(WindowUtils.java:1537) at com.sun.jna.platform.WindowUtils$X11WindowUtils.isWindowAlphaSupported(WindowUtils.java:1487) [catch] at com.sun.jna.platform.WindowUtils.isWindowAlphaSupported(WindowUtils.java:1823) at org.netbeans.core.nativeaccess.NativeWindowSystemImpl.isWindowAlphaSupported(Unknown Source) at org.netbeans.core.windows.FloatingWindowTransparencyManager$1.run(Unknown Source) at java.lang.Thread.run(Thread.java:745) This is apparently caused by a change introduced in 4.2.2-1: > * Renamed the native library to avoid conflicts with other JNA jars used > on the system (LP: #1065253) Workaround: Creating a symlink libjnidispatch.so -> libjnidispatch.system.so fixes this error. Regards, -- YOSHINO Yoshihito <[email protected]> -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages libjna-jni depends on: ii libc6 2.24-9 ii libffi6 3.2.1-6 libjna-jni recommends no packages. libjna-jni suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: libjna-java Source-Version: 4.2.2-3 We believe that the bug you reported is fixed in the latest version of libjna-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg <[email protected]> (supplier of updated libjna-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 12 Apr 2017 10:52:44 +0200 Source: libjna-java Binary: libjna-java libjna-jni libjna-platform-java libjna-java-doc Architecture: source Version: 4.2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Java maintainers <[email protected]> Changed-By: Emmanuel Bourg <[email protected]> Description: libjna-java - Dynamic access of native libraries from Java without JNI libjna-java-doc - Dynamic access of native libraries from Java without JNI (documen libjna-jni - Dynamic access of native libraries from Java without JNI (native libjna-platform-java - Dynamic access of native libraries from Java without JNI (platfor Closes: 858876 Changes: libjna-java (4.2.2-3) unstable; urgency=medium . * Team upload. * Ignore the jna.boot.library.path and jna.boot.library.name properties and always load the system jnidispatch library (Closes: #858876) Checksums-Sha1: deb4fecde77f6733e1846019012b00ec5ed061fe 2390 libjna-java_4.2.2-3.dsc 40319cd1c1433086eeb8602ea6ea445bc52d2edc 10108 libjna-java_4.2.2-3.debian.tar.xz 5b161771261a8e3e28953deca48cb8f59358bfab 11245 libjna-java_4.2.2-3_source.buildinfo Checksums-Sha256: f7060a8502be91d5317931945810660ef22f8120f8ea4d49c660ebc9c6cf6133 2390 libjna-java_4.2.2-3.dsc 4a53418944a322fd94b4ecd881d97443e719cb94092348392a65ad12c46cfb0e 10108 libjna-java_4.2.2-3.debian.tar.xz b8dd44fb4f4a0492f5d04325a0920ed07d6a108d837dfc7d51c07110a8ede25e 11245 libjna-java_4.2.2-3_source.buildinfo Files: bbff7a1e99c1bc03d12f8558d631799f 2390 java optional libjna-java_4.2.2-3.dsc 8f36d19204ebe604dcb2606a626700a1 10108 java optional libjna-java_4.2.2-3.debian.tar.xz 44766b9d47dd81afaa94d643d1d0a883 11245 java optional libjna-java_4.2.2-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJGBAEBCAAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAljt7msSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCspv0P/jF36/8nDiwgDFoDM64BXvJZf5hmxjaO 0FQ85hs+O/2yA30uVADSCl/3PyWCdz3y9a0mJtZ7tx3JMkXl1nP8ln6E3g5B4pKT 4ERfYD13sBR0XfrJ5ErCCrdHgbxS14i5tAXHX+W66/pRWJ1r11TFeQi7DF6XYC5T T4fwU4r/iBQF3XliVq3vufGx1rnf2ExlWKtiB1z+lW3CAAv9hjpygCmsUEfvG2Xx 4tST1pbEDl4lA66dY5arxxUvb01yh3I50po6ayzB1L9DmtCbfoWUR0CI14ByrxOD VT+YaNfeh6wRB+5VBXxeJx+pvQSt0M8yGThe5vOenJdZNMf+OxCP02QTGPSTCu/6 OipBJ+Z4DJ4NB1ZljKSy9Li/XDyQyqkEmHbpEDBX24BkqZhFgBkgJ0LfpVASt1Av HFiphFzZNsQwS9gjws4wogLYHvE2qbb5Rz73PgaQiz5BC9KYa/JIH7m3udpI5RAL LWOyX8AI++IHdtk4zAyvR+w6ba7sFDyAYGEqAmN790/KyFzfdw/cYInxnDPbINz6 ggUcutV3dXIdWCLFAhawSnb4VNHYCG0pcCVytzVj2ZVgQHAHN3fPy3l7JiWBLRTC BmRbP4LEB6a+McmGkmb1/nFFal5bgkk5n7dDMRCtIyxn3Th3YmzEjwYbkHvkZ+rj +tSf30T8mEnx =nhUP -----END PGP SIGNATURE-----
--- End Message ---
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use [email protected] for discussions and questions.
