Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eclipse (Debian) |
Fix Released
|
Unknown
|
|||
| eclipse (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I upgraded from 16.04 to 18.04 on Friday. Following some reboots and updates this morning I am now unable to start the Eclipse IDE. This was working before the upgrade.
I have the C++ developer support added to Eclipse. To the best of my memory (and ability to interrogate apt) it is all installed from the Ubuntu repositories.
When I click the Eclipse launcher pinned to my side bat I get an error message from Eclipse that reads:
An error has occurred. See the log file
/home/thomas/
Viewing the log file I see:
!SESSION Mon Jul 30 11:48:58 BST 2018 -------
!ENTRY org.eclipse.
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.
at java.base/
at java.base/
at java.base/
at org.eclipse.
at org.eclipse.
at org.eclipse.
at org.eclipse.
This is easily repeatable.
Some internet searching suggests this problem is present upstream as there is a Debian bug that looks similar: https:/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eclipse 3.8.1-11
ProcVersionSign
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jul 30 11:43:38 2018
InstallationDate: Installed on 2017-11-16 (255 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitec
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm-
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: eclipse
UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)
| Changed in eclipse (Debian): | |
| status: | Unknown → New |
| Changed in eclipse (Debian): | |
| status: | New → Fix Released |

Reviewing the Debian equivalent people have suggested that:
$ sudo apt-get install --reinstall libequinox-osgi-java
Could resolve the issue. Although some people note that it does not help. Others have recommended completely removing Eclipse as installed through apt and instead using the version supplied directly on the Eclipse CDT webpage https://www.eclipse.org/cdt/
I shall try both solutions this afternoon if there are no alternatives suggested that people would like me to try.