Community
Participate
Working Groups
Steps: 1) Downloaded/installed Eclipse SDK 3.2 RC1a 2) Ran eclipse without -data argument 3) At the workspace prompt, I selected a new workspace /home/johna/callisto-test/ 4) Pointed Eclipse at the Callisto update site (currently download.eclipse.org/callisto/staging/, by tomorrow it will probably be download.eclipse.org/callisto/releases/). 5) Selected to install all features 6) Ok to license and unsigned jar prompts 7) Ok to restart prompt On restart, I got the following error on stdout: _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/wsjarthorne2:0 runCommand: </home/johna/eclipse/eclipse><-name><Eclipse><-exitdata><b000f><An error has occurred. See the log file /home/johna/workspace/.metadata/.log.> Note that the log file was created in a different workspace from the one I was using prior to restarting. Either somebody is writing to the wrong log file, or the wrong workspace is used after restart on update.
This is the stack trace that appeared in the log (in the wrong workspace directory): org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] at org.eclipse.swt.SWT.error(SWT.java:3400) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:788) at org.eclipse.swt.widgets.Display.create(Display.java:776) at org.eclipse.swt.graphics.Device.<init>(Device.java:145) at org.eclipse.swt.widgets.Display.<init>(Display.java:452) at org.eclipse.swt.widgets.Display.<init>(Display.java:443) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:448) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155) at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:122) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:75) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
Note that when I manually restarted, it started fine and chose the correct workspace location. It seems to be just the automatic restart that is not working.
Programmatic restart is IWorkbench API - we are not doing anyting ourselves.
Erich, don't just automatically reassign bugs to us just because you see the keyword 'update' in the title. The bug is about wrong workspace being used after the programmatic use of IWorkbench.restart(), which is in the UI space. It just happens that the call is made from Update, but it does not make it an update bug.
Turns out this is a duplicate of a complex runtime/SWT bug. Dejan, just because you're calling a UI API method, it doesn't mean it's a UI bug either ;) My apologies for not doing a more thorough search before entering this bug. *** This bug has been marked as a duplicate of 106396 ***
No, everything is a UI bug because all the errors are shown in dialogs that belong to JFace :-). What I meant to say is that we are calling IWorkbench.restart() which IS in the UI space, but that does not mean that the trail necessarily ends there. We (Update) just cannot go beyond the API boundary.
