Bugzilla – Bug 130150
Eclipse 3.1 crashes on startup
Last modified: 2006-05-05 13:45:07 UTC
I had Eclipse 3.0 and Java installed using YaST from the original SuSE 9.3 DVD. Then I updated my system to SuSE 10.0 (Eval DVD). Java and Eclipse 3.0 (and some more, like Thunderbird) had been removed by Yast. Very uncool, since I didn't tell tell YaST to remove anything. Actually I was not amused by this, since nowhere on the DVD is written that after installation my Eclipse, Java and Tunderbird is removed from HDD. So I added an FTP mirror as installation source and used YaST to reinstall Java, rebooted, then reinstalled Eclipse and Thunderbird. Java is running (1.4.2 and 1.5.0), also Thunderbird is working well. But Eclipse 3.1 crashes on startup, telling me that a class is not found. What to do now? When will this be fixed? I need a working Eclipse immediately and I don't want to download the original Eclipse jast after having obtained a brand new SuSE DVD...?! The bug report is: java.lang.NoSuchMethodError: org.eclipse.swt.internal.gtk.OS.GTypeInfo_sizeof()I at org.eclipse.swt.internal.gtk.GTypeInfo.<clinit>(GTypeInfo.java:26) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:777) at org.eclipse.swt.widgets.Display.create(Display.java:746) at org.eclipse.swt.graphics.Device.<init>(Device.java:141) at org.eclipse.swt.widgets.Display.<init>(Display.java:429) at org.eclipse.swt.widgets.Display.<init>(Display.java:420) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:394) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155) at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:128) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:79) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948)
Is the symlink for /usr/share/java/swt-gtk-3.1.jar broken? It should be pointing at /usr/share/eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.1.0.jar. If this is broken, then you should install/reinstall libswt3-gtk2.
I checked the symlink /usr/share/java/swt-gtk-3.1.jar and it points to /usr/share/eclipse/org.eclipse.swt.gtk.linux.x86_3.1.0.jar as it should Also I tried 'jar -tf /usr/share/swt-gtk-3.1.jar' and it worked well (listed up the jar content without complaining in any way). I also used YaST to reinstall libswt3-gtk2, but it didn't improve anything. The problem ist still there, with the same log entry.
I can't reproduce this (which is why it has been lying around until now). Carrying over to 10.1 for: 1) retesting the update issue 2) trying to reproduce the crash on 10.1
Has anyone retested this on/with 10.1? If this is no longer a problem and/or as there has been no activity for 4 months I would close it unles the reporter has a problem with this. The status should also not be "New" ...
No, I did not test it with 10.1. I will now do the following: Install a 9.3 system with eclipse and do an update to 10.1 after that. If eclipse will run, I will close the bug. Regards, Daniel
Ok, I installed 9.3 from scratch and updated to 10.1RC3. Everything worked and eclipse started without an error. ... I think we should close the bug for now as it worked for me doing an update from 9.3->10.1. Note that we don't update the 10.0 packages if it is not a security issue. If by tonight nobody objects, I will close this bug. Best regards, Daniel
Closing for now ... if anybody can recreate the bug and provide me with more info, please re-open it.