Bug 1877348 - JDK 11.0.9 cannot start upstream Eclipse 2020-06
Summary: JDK 11.0.9 cannot start upstream Eclipse 2020-06
Keywords:
Status: CLOSED DUPLICATE of bug 1869017
Alias: None
Product: Fedora
Classification: Fedora
Component: java-11-openjdk
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-09 12:34 UTC by Richard Chan
Modified: 2020-09-17 09:19 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-17 09:19:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Eclipse JVM error dialog box (229.84 KB, image/png)
2020-09-09 12:34 UTC, Richard Chan 		no flags Details
View All

Description Richard Chan 2020-09-09 12:34:46 UTC 
Created attachment 1714272 [details]
Eclipse JVM error dialog box

Description of problem:
Fedora 33's JDK 11 cannot run upstream's eclipse (Eclipse 2020-06 from eclipse.org)


Version-Release number of selected component (if applicable):
java-11-openjdk-11.0.9.1-0.1.ea.fc33.x86_64
eclipse-java-2020-06-R-linux-gtk-x86_64.tar.gz

How reproducible:
Always


Steps to Reproduce:
1. Install java-11-openjdk{,-devel,-headless,-jmods}
2. Unpack upstream Eclipse 2020-06: to eclipse/
3. Run eclipse/eclipse

Actual results:
Error: LinkageError occurred while loading main class org.eclipse.equinox.launcher.Main
        java.lang.ExceptionInInitializerError: null



Expected results:
Eclipse runs normally

Additional info:
Comment 1 Richard Chan 2020-09-09 12:58:57 UTC 
Downgrading to java-11-openjdk-11.0.8.10-1.fc33.x86_64 fixes upstream eclipse startup.
Comment 2 Severin Gehwolf 2020-09-17 09:19:43 UTC 
Yes, this is an issue with java-11-openjdk-11.0.9.1-0.1.ea.fc33.x86_64 which got fixed with java-11-openjdk-11.0.9.6-0.1.ea.fc33.x86_64 and better. Sorry about the trouble.

*** This bug has been marked as a duplicate of bug 1869017 ***
Note You need to log in before you can comment on or make changes to this bug.