Created attachment 1337260 [details] eclipse .log file Description of problem: After 'dnf update', eclipse fails to start. See attached .log. (Note sure if this should be assigned to 'eclipse' or 'eclipse-cdt'..) Version-Release number of selected component (if applicable): Installed Packages eclipse-abrt.noarch 0.0.3-2.fc26 @@commandline eclipse-cdt.x86_64 1:9.3.2-2.fc26 @updates eclipse-cdt-native.x86_64 1:9.3.2-2.fc26 @updates eclipse-cdt-parsers.x86_64 1:9.3.2-2.fc26 @updates eclipse-color-theme.noarch 1.0.0-6.fc26 @@commandline eclipse-dltk.noarch 5.8.1-1.fc26 @updates eclipse-dltk-sh.noarch 5.8.1-1.fc26 @updates eclipse-dtp.noarch 1.14.0-1.fc26 @updates eclipse-ecf-core.noarch 3.13.8-1.fc26 @updates eclipse-egit.noarch 4.8.0-2.fc26 @updates eclipse-emf-core.noarch 1:2.13.0-2.fc26 @updates eclipse-emf-runtime.noarch 2.13.0-2.fc26 @updates eclipse-epp-logging.noarch 2.0.6-1.fc26 @updates eclipse-equinox-osgi.x86_64 1:4.7.1-4.fc26 @updates eclipse-filesystem.noarch 1.0-9.fc26 @updates eclipse-gef.noarch 3.11.0-3.fc26 @updates eclipse-jdt.noarch 1:4.7.1-4.fc26 @updates eclipse-jgit.noarch 4.8.0-2.fc26 @updates eclipse-launchbar.noarch 1:2.1.2-2.fc26 @updates eclipse-linuxtools.noarch 6.1.1-2.fc26 @updates eclipse-linuxtools-changelog.noarch 2:6.1.1-2.fc26 @updates eclipse-linuxtools-libhover.noarch 6.1.1-2.fc26 @updates eclipse-linuxtools-manpage.noarch 6.1.1-2.fc26 @updates eclipse-linuxtools-rpm-editor.noarch 6.1.1-2.fc26 @updates eclipse-m2e-core.noarch 1.8.1-1.fc26 @updates eclipse-m2e-workspace.noarch 0.4.0-5.fc26 @fedora eclipse-mylyn.noarch 3.23.1-6.fc26 @updates eclipse-mylyn-context-cdt.noarch 3.23.1-6.fc26 @updates eclipse-mylyn-docs-wikitext.noarch 3.23.1-6.fc26 @updates eclipse-mylyn-tasks-bugzilla.noarch 3.23.1-6.fc26 @updates eclipse-mylyn-versions.noarch 3.23.1-6.fc26 @updates eclipse-p2-discovery.noarch 1:4.7.1-4.fc26 @updates eclipse-pde.x86_64 1:4.7.1-4.fc26 @updates eclipse-platform.x86_64 1:4.7.1-4.fc26 @updates eclipse-ptp.x86_64 9.1.3-1.fc26 @updates eclipse-recommenders.noarch 2.4.9-2.fc26 @updates eclipse-remote.noarch 3.0.0-0.1.git96f33c6.fc26 @updates eclipse-rse.noarch 3.7.3-1.fc26 @updates eclipse-swt.x86_64 1:4.7.1-4.fc26 @updates eclipse-tm-terminal.noarch 4.3.0-0.2.gitfa298da.fc26 @updates eclipse-tm-terminal-connectors.noarch 4.3.0-0.2.gitfa298da.fc26 @updates eclipse-usage.noarch 4.5.0-1.fc26 @updates eclipse-webtools-common.noarch 3.9.0-1.fc26 @updates eclipse-webtools-javaee.noarch 3.9.0-1.fc26 @updates eclipse-webtools-servertools.noarch 3.9.0-1.fc26 @updates eclipse-webtools-sourceediting.noarch 3.9.0-1.fc26 @updates eclipse-xsd.noarch 2.12.0-2.fc26 @@commandline How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug should be against eclipse proper. From the trace, there is a failure with LegacyIDE.e4xmi. This may be a configuration issue after updating. I would suggest you try moving your .eclipse folder to a temporary location (.eclipseold for example), and then start eclipse again and see if that solves the problem.
yup, renaming ~/.eclipse does seem to get it working again.
Same problem hit me today, same solution worked.
Happened to me after upgrade from fedora 27 to 28. Workaround worked.
Created attachment 1430117 [details] eclipse .log file fedora 28
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'm somehow not able to change the version to f28. Could someone else do this?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.