Bug 1385212 - [eclipse] aborts after selecting the workspace
Summary: [eclipse] aborts after selecting the workspace
Keywords:
Status: CLOSED DUPLICATE of bug 1392150
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-15 08:40 UTC by Joachim Frieben
Modified: 2016-11-09 20:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-09 20:41:38 UTC
Type: Bug


Attachments (Terms of Use)
Eclipse error log file (14.63 KB, text/plain)
2016-10-15 08:40 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2016-10-15 08:40:40 UTC
Created attachment 1210748 [details]
Eclipse error log file

Description of problem:
For current Fedora 25, eclipse aborts after selecting the workspace. Instead, an error message pops up pointing to a log file which is attached to this bug report.

Version-Release number of selected component (if applicable):
eclipse-4.6.1-5.fc25

How reproducible:
Always

Steps to Reproduce:
1. Run 'eclipse' in a shell.

Actual results:
After selecting the workspace, an error window pops up.

Expected results:
Eclipse starts up successfully.

Additional info:
No corresponding entry is found in the bug reporting tool.

Comment 1 Mat Booth 2016-10-15 09:30:49 UTC
I cannot reproduce this... Can you try running "eclipse -clean" or moving your ~/.eclipse directory to see if one of these fixes it?

Comment 2 Christian Stadelmann 2016-10-15 12:04:50 UTC
I ran into this bug too after upgrading to eclipse-swt-4.6.1-5.fc25.x86_64. The last backtrace is exactly the same and I'm getting tens of "Unresolved requirement" messages before that.

Got rid of it by starting eclipse with "-clean" parameter, then it started without issues. After that I am able to start eclipse without the "-clean" parameter. No error messages in log file any more.

Comment 3 Roland Grunberg 2016-10-25 15:11:25 UTC
I have had similar behaviour in the past but very little time to investigate. I initially suspected this was related to using 2 different Eclipse instances (eg. rpm or upstream) on the same workspace (even if they are the same version of Eclipse).

Comment 4 Joachim Frieben 2016-10-25 18:56:37 UTC
(In reply to Roland Grunberg from comment #3)
The only eclipse installed on my systen has been pulled in through dnf. As pointed out correctly in comment 1, removing directory .eclipse/ allows for a clean start-up of eclipse thereafter.

Comment 5 Roland Grunberg 2016-11-09 20:41:38 UTC
I think this is exactly Bug 1392150. I've reproduced and think it's related to how bundles wire to javax.annotation (there are 2 providers : one from javax.annotation-api and one from the system bundle).

*** This bug has been marked as a duplicate of bug 1392150 ***


Note You need to log in before you can comment on or make changes to this bug.