Bug 1702624

Created attachment 1558052 [details]
Error log

Error log

Running Fedora 29 (KDE with the Breeze dark theme)

After installing the eclipse package it worked properly.
Installing the eclipse-cdt package on top caused it to be unable t launch (error messages in attachment)

Removing the ~/.eclipse directory seems to have fixed this issue.

Hmm, FWIW I can reproduce this in a standard gnome session

There are a bunch of SWT errors.  Eric, can you comment on any SWT changes recently whereby clearing .eclipse would fix the issues?

Ugh, comedy OSGi dep wiring strikes again:

Before installation of eclipse-cdt, all consumers of javax.annotations are wired to the JRE implementation. (Everything works.)

After installation of eclipse-cdt there appears to be bundles wired to two different versions of the javax.annotations, JRE and glassfish. (Error occurs.)

After doing a "eclipse -clean" all bundles are once again wired to a single implementation. (Everything works.)

(In reply to Mat Booth from comment #5)
> Ugh, comedy OSGi dep wiring strikes again:
> 
> Before installation of eclipse-cdt, all consumers of javax.annotations are
> wired to the JRE implementation. (Everything works.)
> 
> After installation of eclipse-cdt there appears to be bundles wired to two
> different versions of the javax.annotations, JRE and glassfish. (Error
> occurs.)
> 
> After doing a "eclipse -clean" all bundles are once again wired to a single
> implementation. (Everything works.)

If not easily fixable, can we run eclipse -clean post-install to save the
end-user running into such issues?

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.