| Summary: | Can’t launch Eclipse Oxygen 1a on Ubuntu Mate 16.04 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Val Nyrov <nvg.dev> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, gayanper, loskutov, lufimtse |
| Version: | 4.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Val Nyrov
My current configuration is: OpenJDK: openjdk version "9-internal" OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src) OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode) Ubuntu: x86_64 GNU/Linux Ubuntu Mate 16.04 4.4.0-98-generic Eclipse Oxygen rc4 works fine, but after update it not start: JVM terminated. Exit code=1 /usr/bin/java -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -jar /home/nvg/Programm/eclipse1//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar -os linux -ws gtk -arch x86_64 -showsplash /home/nvg/Programm/eclipse1//plugins/org.eclipse.epp.package.common_4.7.1.20171005-1200/splash.bmp -launcher /home/nvg/Programm/eclipse1/eclipse -name Eclipse --launcher.library /home/nvg/Programm/eclipse1//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.550.v20170928-1359/eclipse_1629.so -startup /home/nvg/Programm/eclipse1//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar --launcher.appendVmargs -exitdata 7c8018 -product org.eclipse.epp.package.cpp.product -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -jar /home/nvg/Programm/eclipse1//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar I downloaded the new version -Oxygen 1a, but the problem is the same: VM terminated. Exit code=1 /usr/bin/java -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -jar /home/nvg/Programm/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar -os linux -ws gtk -arch x86_64 -showsplash /home/nvg/Programm/eclipse//plugins/org.eclipse.epp.package.common_4.7.1.20171005-1200/splash.bmp -launcher /home/nvg/Programm/eclipse/eclipse -name Eclipse --launcher.library /home/nvg/Programm/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.550.v20170928-1359/eclipse_1629.so -startup /home/nvg/Programm/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar --launcher.appendVmargs -exitdata 80801d -product org.eclipse.epp.package.cpp.product -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -jar /home/nvg/Programm/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar If you launch it from the Terminal, does it produce some kind of crashlog of sorts? Hi! Launch "Oxygen 1a" from terminal: $ ./eclipse Unrecognized option: --add-modules=ALL-SYSTEM Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. and I did not see the log files either in the "eclipse_workspace/.metadata" directory or in the "eclipse/configuration" directory p.s. Oxygen-1-rc4 still works fine on the same configuration Yours faithfully, Valeriy (In reply to Val Nyrov from comment #3) > Hi! > > Launch "Oxygen 1a" from terminal: > $ ./eclipse > Unrecognized option: --add-modules=ALL-SYSTEM > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > Gtk-Message: GtkDialog mapped without a transient parent. This is > discouraged. > > and I did not see the log files either in the "eclipse_workspace/.metadata" > directory or in the "eclipse/configuration" directory > > p.s. Oxygen-1-rc4 still works fine on the same configuration > > > Yours faithfully, > Valeriy Which jdk is linked to /usr/bin/java? Looks like the launcher sees the Java 9 but path contains Java 8. that's what I see: $ sudo update-alternatives --display java java - auto mode link best version is /usr/lib/jvm/java-9-openjdk-amd64/bin/java link currently points to /usr/lib/jvm/java-9-openjdk-amd64/bin/java link java is /usr/bin/java slave java.1.gz is /usr/share/man/man1/java.1.gz /usr/lib/jvm/java-9-openjdk-amd64/bin/java - priority 1091 slave java.1.gz: /usr/lib/jvm/java-9-openjdk-amd64/man/man1/java.1.gz $ ls -l /usr/bin/java* /usr/bin/java -> /etc/alternatives/java $ ls -l /etc/alternatives/java* /etc/alternatives/java -> /usr/lib/jvm/java-9-openjdk-amd64/bin/java /etc/alternatives/java.1.gz -> /usr/lib/jvm/java-9-openjdk-amd64/man/man1/java.1.gz OK, what does "java -version" reports if executed from same shell? Can it be that you run some early 9 beta release? java version: $ java -version openjdk version "9-internal" OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src) OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode) (In reply to Val Nyrov from comment #7) > java version: > > $ java -version > openjdk version "9-internal" > OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src) > OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, > mixed mode) Have you tried to ask your package manager to update Java 9? I don't know if this beta supports the final Java 9 arguments syntax, most likely not, because it changed few times. AFAIK we have 2017 today, and the beta of Java 9 from 2016-04 can be considered as unsupported and obsoleted crap. You are right, I installed the new version OpenJDK 9.0.1 and it worked! Problem solved, thank you very much! *** Bug 533326 has been marked as a duplicate of this bug. *** |