Comment 11 for bug 1055159

I've got the same error on starting eclipse from the console.

But I had slightly different message:
# JRE version: 7.0_13-b20
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgobject-2.0.so.0+0x192c0] g_object_get_qdata+0x20

Starting eclipse from the desktop icon fails (with crash directly after workspace selection.)

Strange thing - after executing command mensioned in the error message ("ulimit -c unlimited"), starting eclipse succeeded. That was first eclipse execution after installation and I tried to select a non-default workspace with one unpacked python-project in it (located on ntfs-partition).
So I could install pydev extension to eclipse and wanted to test it one more time.

Starting from desktop still was not possible, starting from the same terminal for default workspace (to be initialized) succeeded one more time. Starting eclipse from another terminal failed.

General repitition:
- exit from terminal
- starting via desktop launcher failed after non-default workspace location
- start terminal
- starting eclipse from terminal crashes the same way
- execute "ulimit -c unlimited"
- starting eclipse from terminal !!!CRASHES!!! :(:(:(

It looks like really annoying hard bug...