Bug#863337: visualvm: Typos in launcher script - does not start anymore
Package: visualvm Version: 1.3.9-1 Followup-For: Bug #863337 Dear Maintainer, I am also seeing this issue: $ java -version openjdk version "1.8.0_171" OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-1~deb9u1-b11) OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode) $ visualvm Unknown option -L-XX:PermSize=32m $ grep -r PermSize ~/.visualvm /etc/visualvm/visualvm.conf /usr/lib/jvm/*/lib/visualvm/etc/visualvm.conf $ All the best, Mark -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (600, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages visualvm depends on: ii default-jdk [java7-sdk] 2:1.8-58 pn libnb-platform18-java ii libvisualvm-jni 1.3.9-1 ii openjdk-10-jdk [java7-sdk]10.0.1+10-4 ii openjdk-8-jdk [java7-sdk] 8u171-b11-1~deb9u1 ii openjdk-9-jdk [java7-sdk] 9~b181-4~bpo9+1 ii oracle-java8-jdk [java7-sdk] 8u131 visualvm recommends no packages. visualvm suggests no packages. -- no debconf information
Bug#863337: visualvm: Typos in launcher script - does not start anymore
Le 5/07/2017 à 13:07, Erich Schubert a écrit : > To me, these appear to be obvious typos; independent of whether you can > reproduce them, or not... This was changed by upstream in the latest version: https://github.com/visualvm/visualvm/commit/d6026fc5 These options are passed to nbexec, and the -L flag stands for "Launcher options". So I'm not convinced this is a typo. See: http://sources.debian.net/src/netbeans/8.1%2Bdfsg3-2/o.n.bootstrap/launcher/unix/nbexec/?hl=99#L143 If this really causes a problem on your system I suggest reporting this to upstream. If they confirm the error we'll backport the fix. Emmanuel Bourg
Bug#863337: visualvm: Typos in launcher script - does not start anymore
Hi, I will try to double-check this, but I'm constantly short on time these days. I didn't modify visualvm.conf But by any means, by looking at the source don't you think it should be -J rather than -L? Even if e.g. the bug only appears because Java 9 fails to start with -L, whereas maybe java 8 maybe silently ignored them? To me, these appear to be obvious typos; independent of whether you can reproduce them, or not... Regards, Erich On Sun, May 28, 2017 at 10:58 AM, Chris Lambwrote: > Hey Erich, > > > visualvm: Typos in launcher script - does not start anymore > > I can't seem to reproduce this on a fresh stretch or sid chroot. Can you > paste your /etc/visualvm/visualvm.conf? Is this an upgrade? My chroots > seem to be using OpenJDK if that helps. > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- >
Bug#863337: visualvm: Typos in launcher script - does not start anymore
On Thu, May 25, 2017 at 04:50:56PM +0200, Erich Schubert wrote: > Package: visualvm > Version: 1.3.9-1 > Severity: grave > Justification: renders package unusable > > visualvm does not start anymore with the error: > Unknown option -L-XX:PermSize=32m > Versions of packages visualvm depends on: > ii default-jdk [java7-sdk]2:1.8-58 > ii libnb-platform18-java 8.2+dfsg1-1 > ii libvisualvm-jni1.3.9-1 > ii openjdk-8-jdk [java7-sdk] 8u131-b11-2 > ii openjdk-9-jdk [java7-sdk] 9~b170-2 ^^^ Hello Erich, Just as Chris reported, I am also unable to reproduce this behavior on my stretch or sid systems. I notice that you have openjdk-9-jdk installed. Is it possible that a Java 9 JRE is on your path and being invoked? In any event, I'm tagging this +moreinfo. Please share more information about your configuration when you can. Thank you, tony
Bug#863337: visualvm: Typos in launcher script - does not start anymore
Hey Erich, > visualvm: Typos in launcher script - does not start anymore I can't seem to reproduce this on a fresh stretch or sid chroot. Can you paste your /etc/visualvm/visualvm.conf? Is this an upgrade? My chroots seem to be using OpenJDK if that helps. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#863337: visualvm: Typos in launcher script - does not start anymore
Package: visualvm Version: 1.3.9-1 Severity: grave Justification: renders package unusable visualvm does not start anymore with the error: Unknown option -L-XX:PermSize=32m This is caused by a trivial typo in the start script, which supposedly should use -J (like "Java options") instead of -L (two locations): visualvm_default_options="-L-XX:PermSize=32m ${visualvm_default_options}" should likely be visualvm_default_options="-J-XX:PermSize=32m ${visualvm_default_options}" In particular, note that the if statement reads 'if grep -v -- "-J-XX:MaxPermSize"' -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages visualvm depends on: ii default-jdk [java7-sdk]2:1.8-58 ii libnb-platform18-java 8.2+dfsg1-1 ii libvisualvm-jni1.3.9-1 ii openjdk-8-jdk [java7-sdk] 8u131-b11-2 ii openjdk-9-jdk [java7-sdk] 9~b170-2 visualvm recommends no packages. visualvm suggests no packages. -- no debconf information