Ubuntu
eclipse package

eclipse fails to start in Feisty, SIGSEGV in libgobject

Bug #83031 reported by Mikael Olenfalk on 2007-02-03

Affects		Status	Importance	Assigned to	Milestone
	eclipse (Ubuntu)	Fix Released	Medium	Ralph Janke

Bug Description

Binary package hint: eclipse

Eclipse fails to start both from eclipse.org (eclipse callisto and eclipse 3.3M4) with a sigsegv in libgobject-2.0 error log and stacktrace from eclipse follows

Revision history for this message

Mikael Olenfalk (mikael-olenfalk) wrote on 2007-02-03:

eclipse log file of the crash Edit (38.2 KiB, text/plain)

this is the eclipse log fail

Revision history for this message

Ari Johannesson (arividar) wrote on 2007-06-21:

I am getting the same error and have exhausted all options in launching Eclipse with different JVMs. What I need is to be able to run eclipse under Sun JVM 5 or 6 but I always get this error. I am running Feisty on 64bit AMD.

Has anybody found a workaround?

Revision history for this message

Ralph Janke (txwikinger) wrote on 2008-04-20:

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the development release - Hardy Heron. I was not able to reproduce this with Hardy.

It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ .

Thanks again and we appreciate your help.

Changed in eclipse:
assignee:	nobody → txwikinger
status:	New → Incomplete
importance:	Undecided → Medium

Revision history for this message

Ralph Janke (txwikinger) wrote on 2008-06-06:

It seems that this problem has been fixed in the latest release.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!