AnsweredAssumed Answered

CCES won't launch, Eclipse SWT library error

Question asked by jon_harris8 on Feb 20, 2017
Latest reply on Feb 22, 2017 by jon_harris8

I am working with a fresh install of CCESS 2.5.0 for Linux on Ubuntu.  When I try to launch the IDE, I get this error:

An error has occurred. See the log file
/opt/analog/cces/2.5.0/Eclipse/configuration/1487625496005.log.

 

Opening that log file, here is what I get, with errors in red:

 

!SESSION 2017-02-20 13:18:15.921 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_102
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86

!ENTRY org.eclipse.osgi 4 0 2017-02-20 13:18:16.925
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
 /opt/analog/cces/2.5.0/Eclipse/configuration/org.eclipse.osgi/376/0/.cp/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
 no swt-pi-gtk in java.library.path
 /home/jharris/.swt/lib/linux/x86/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
 Can't load library: /home/jharris/.swt/lib/linux/x86/libswt-pi-gtk.so

 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:327)
 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
 at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:38)
 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
 at org.eclipse.swt.widgets.Display.<clinit>(Display.java:134)
 at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:734)
 at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:162)
 at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:169)
 at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:111)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

 

Any ideas on how to fix this?

Outcomes