Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1579902

Summary:	unable to start eclipse.
Product:	[Fedora] Fedora	Reporter:	Jeremy Linton <jeremy.linton>
Component:	eclipse	Assignee:	Mat Booth <mat.booth>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	28	CC:	akurtako, ebaron, jerboaa, lef, mat.booth, rgrunber
Target Milestone:	---
Target Release:	---
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-18 16:29:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	245418

Description Jeremy Linton 2018-05-18 15:28:31 UTC

Description of problem: eclipse fails with "The Eclipse executable launcher was unable to locate it companion shared library"


Version-Release number of selected component (if applicable):

eclipse-platform-4.7.3a-4.fc28
maybe related?
java-1.8.0-openjdk-1.8.0.171-4.b10.fc28


How reproducible: 100% 


Steps to Reproduce:
1. install eclipse
2. attempt to start it
3.

Actual results:
eclipse starts?

Additional info:

A quick google search, yields a lot of results similar to this, mostly on windows and the suggested fix is to reinstall, (which I did as this machine has been upgraded from F26-F27-F28) and the problem still exists. A quick strace seems to indicate a few open failures here and there, but it mostly looks like probing as many of the .so's that are failing are eventually found.

Comment 1 Mat Booth 2018-05-18 16:29:19 UTC


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