I'm trying to get Eclipse to work on my CentOS 7 VM via X11 forwarding. The X11 forwarding seems to be working, as I am able to run and see "xclock". However, whenever I run Eclipse, it crashes with a message similar to this:
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/home/centos/eclipse/configuration/org.eclipse.osgi/375/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/centos/.swt/lib/linux/x86_64/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/centos/.swt/lib/linux/x86_64/libswt-pi-gtk.so
This issue is all over the web, and a lot of it is solved my soft linking files in /usr/lib/jni/ to ~/.swt/lib/linux/x86/ but, I do not have a a /usr/lib/jni directory. So, I tried to find the libraries that create this folder upon installation and I found these in another Stack Overflow post: libswt-gtk-3-jni, libswt-gtk-3-java
And I can't seem to find anything on CentOS that provides these. I then found this guide on the CentOS client portal for installing Eclipse and it doesn't work for me. It talks about getting access to devtoolset-3 via RedHat Subscription Manager or RHN Classic, both of which are unavailable to me on the machine that I am working with.
At this point I have JDK installed, and Eclipse untarred and attempting to launch and I'm getting this error. Any ideas?
Related
I downloaded the latest eclipse setup and tried to install it in my PC, but I get this error
NLS missing message: ECLIPSE_STARTUP_ERROR_CHECK_LOG in: org.eclipse.osgi.internal.messages.ExternalMessages
But when I used the same setup file in another PC, it got installed. Here both the PCs are installed with the same version of the Windows 10 and the Hardware is identical.
Now what am I missing here that I am unable to install it.
Before I posted this question I saw a lot of similar question related to the same error with Eclipse. But for those all problems the error occurred after installing the Eclipse while opening the workspace. Hence the solution given to them don't work much for me.
For me I get this error the moment I run the setup.
I faced the same issue. I found that the zip was not correctly extracted. Try to unzip with any uncompressing software like 7zip
Delete the previous eclipse folder. Open eclipse again. It will immediately work.
I have been using Linux for less than 24 hours, so please, if there is anymore information I should provide, do be quite specific about how to get that information.
I've been trying to install Node.js, express.js and eclipse. As you can see, ubuntu does recognise both node.js and express as installed on my system (I think!) and I got the Nodeclipse-extension for eclipse, but still Eclipse doesn't seem to recognise either node.js or express (see my image below). I also want to add that the time occurrence of the error, I was trying to build a Node.js Express Project.
At this point, how do I go about debugging the situation? The folder location shown in the image does not fully exist. I can only go as far as [...]/bin/ - I have been looking at error messages similar to mine, and it seems like people are getting such errors because they're lacking an installation, however, from my screenshot provided, I would think everything is installed as needed.
I am using a native 64-bit windows laptop with Linux (Ubuntu) installed through a virtualbox. Ubuntu is 14.04 LTS and just 32-bit, as I don't have spare 2 gb ram to give the 64-bit version. Sadness.
I'd appreciate any help!
In Eclipse Windows -> Preferences -> Nodeclipse
check what is configured for Node and Express
Read more on http://www.nodeclipse.org/
I found a solution, which worked for me:
WINDOWS:
I did double installations of the needed modules. They were both located in C:/Users/X/AppData/Roaming, in the Eclipse directories and finally in C:/Program Files/nodejs. When I deleted all the node_modules, besides critical ones for nodejs to function and then ran Eclipse with Nodeclipse, it seemed to function and Eclipse automaticly defined folders in its own subdirectory, in which Express were located.
UBUNTU:
Delete all node_modules files and run Eclipse with Nodeclipse. See the windows explanation for a more detailed overview. Same problem and solution seemed to be present for both systems. Do note that the file directories are of course not completely interchangeable. You'll need to locate your instances of node_module.
I am running a virtualbox with debian installed as local webserver. I am working with eclipse directly on that virtual box with a remote project (RSE plugin). I am having the problem that eclipse starts the DLTK-indexer as soon as I open the project. On the debian machine, instantly my /var/log/auth.log is filling up with a endless list of:
sshd[4271]: error: no more sessions
In eclipse, the error log is filling up with (although using JRE 6):
org.eclipse.core.runtime.CoreException: Operation failed. File system input or output error: rse://xxx.xxx.xxx.xxx/path/to/file/being/indexed
org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
While indexing is done, I am not able to save any file I am working on, as all ssh-sessions are already used on the server.
It seems that the indexing process tries to open a new connection for every file it´s indexing.
When indexing is finished, everything works normal again, I can save files etc.
I would appreciate the indexer to complete its work, but as code completion does not work afterwards, eclipse was not able to do the indexing.
One solution would be to disable the indexing, but this is not the purpose of an IDE, code completion is one of the few reasons for me to still use an IDE (at least for large projects).
Any ideas on how to make indexing work and get rid of the ssh-errors would be great!
Futher system information:
Host-System: Windows 7 Prof. 64bit
Guest-System (virtualbox): Debian Lenny with sftp subsystem enabled
Eclipse: Indigo with Zend PDT and RSE (already running with Java 6 JRE 1.6.0_45)
Thanks for your help!
David
I was able to fix this issue by doing two things:
set up ssh to use multiplexing (see http://en.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexing) in the virtual machine
Upgrade eclipse to Kepler 64Bit release (much faster and more stable in Windows 7) with manual installation of PDT feature (using Zend PDT is a waste of time)
This also works with Java7!
Now I have completely indexed projects and can use code-completion!
I'm trying to install ADT plug-in in Eclipse 3.5.2 which I got from PowerPC Ubuntu repositories. ADT 16.0.0 or above requires Eclipse 3.6 or higher so I tried 15.0.1 and 9.0.0.
ADT 15.0.1 installation completed 100%, I clicked "Apply Now" and got a bunch of errors. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Problems occurred when invoking code from plug-in: "org.eclipse.ui.intro".
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
ADT 9.0.0 Installation went the same. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.gef_3.5.1.v20090910-2020.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.draw2d_3.5.2.v20091126-1908.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
Android tab did not appear in Window > Preferences.
Also, both installations took 2 hours.
So, is it possible to install ADT plug-in to Eclipse on PowerPC Ubuntu? Is there any way to install Eclipse 3.6 or 3.7 on my system? My computer is PowerPC G4, Emac (ATI Graphics), Ubuntu 10.04.
First, never install Eclipse from a Linux package manager or repository; always download from www.eclipse.org
The PowerPC linux builds are only available for the Eclipse SDK, not the packages listed on the main Eclipse Downloads page. Here's the link for the latest release of Eclipse (3.7.2/Indigo): http://download.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/index.php
The other thing to make sure of is that you have the Oracle JDK and have configured Eclipse to use it, as described here. Most Linux distros have gcj on the system path and it doesn't play nice with Eclipse.
From there you should be able to install the ADT according to the instructions.
I will throw in here just in case someone runs across my problem
Mint 32 bit, all updates and upgrades applied
sudo apt-get updates
sudo apt-get upgrades)
Eclipsed Indigo Classic - sudo apt-get eclipse
java - sudo apt-get install sun-java6-jdk
Trying to install the Android Eclipse Plugin r18 continually failed with the org.eclipse.wst.sse.core missing error that seems common and random at the same time. Note, this did not happen using 64 bit mint/eclipse etc. go figure. and never on windows.
Here is what I did after trying a lot of different patterns found here on Stack and experimenting using snaps on a virtual box to find the right recipe for me.
Fresh eclipse classic indigo install 3.7.0 (sudo apt-get eclipse) as mentioned above
Start eclipse from the command (sudo eclipse)
Add the repository http://download.eclipse.org/releases/indigo in the Help/Install New Software section
Install Linux tools from the list of options from step 3
After restart try to install the android tools again from the http://dl-ssl.google.com/android/eclipse/ repository ( Success !!! )
After restart CLOSE eclipse (don't let it install the sdk etc)
Start Eclipse normally and let the tools install the SDK for you, or click on the "Window" menu if it doesnt do this immediately on restart to install the base sdk package
Go to the Android SDK manager under the window menu and download any other api's etc you need
This worked for me, many similar things did not, not sure what the differences where etc. and also note I had ZERO issues using 64 bit mint (which is a bit counter intuitive considering the problems the ADB has with 64 bit)
Not THE answer, but certainly an answer for someone having same issues I was (Hopefully)
I've manually installed the latest Eclipse on our debian server and wanted to configure it so all users share the same configuration. It turned out less obvious than I thought: I don't seem to be able to install packages for all users. If I run it myself, all configuration data is saved under my own home directory. If I run Eclipse using sudo, everything is saved under the root directory but is not accessible for other users when they run Eclipse.
I've been browsing the manual of Eclipse and some forums, but apart from a "yes, you can" I couldn't find any information on how that should be done. The biggest problem is installing plugins for all users to be found. Any help is greatly appreciated.
Eclipse : 3.6.1 classic, installed using this procedure.
Server uname: GNU/Linux *** 2.6.26-2-amd64
Server is accessed using Putty, and Gnome desktop through realVNC. Just mentioning it if that is of any importance. Our sysadmin is on "prolonged leave" (working in Spain and never replaced), so I'm stuck without help here.
EDIT:
I've found a list of variables that could be set in the launcher.ini or config.ini regarding configuration : osgi.configuration.area, osgi.configuration.area.default, osgi.sharedConfiguration.area, osgi.configuration.cascaded, ... But I can't figure out exaclty how to set these correctly.
-- I asked this question also on Serverfault, but I am far from certain where this belongs. Feel free to merge both questions in the appropriate place. --
For plugins, you could add in eclipse.ini (for all Eclispe you install) a common path for "shared dropins directory".
All plugins copied in that directory will be detected when Eclipse is launched.