I needed to install ibus on Ubuntu 19.04 LTS and shortly after doing so I started getting this error when trying any file in Eclipse 2019.
org.eclipse.swt.SWTError: No more handles
I tried installing the newest version thinking something broke in Eclipse, but I couldn't even install because I got the same error in the installer.
I didn't realize right away that ibus was the cause because I didn't try using Eclipse for several hours after installing it.
After a lot of searching and trying just about everything, the answer turned out to be the need to set the GTK mode before launching Eclipse.
export GTK_IM_MODULE="ibus"
To make my life easier in the future, I created a script file to do this any time I started Eclipse. This is a simple text file with the executable flag set.
#/bin/bash
export GTK_IM_MODULE="ibus"
~/Programs/eclipse/php-2019-03/eclipse/eclipse
I hope this saves others a great deal of searching.
Related
I wanted to use Visual Studio Code for HaxeFlixel development and the Haxe extension noted that I needed Haxe 3.4.0. I went ahead and downloaded the new installer from the website and installed it on my laptop running Windows 10. However after installing it turned out that calling 'haxelib version' in the command prompt it still returned 3.3.0.
I tried rebooting. Uninstalling then rebooting and installing again. I could find nothing in the system environmental variables that could cause it. Tried updating the Haxe on my Desktop, and had the same issue. Which is running windows 8.1 on it.
Does someone know what might be the cause? Thank you for your time in advance.
To check the Haxe version, use haxe -version. haxelib is a separate application and can have a version number that's different from the compiler's version.
Haxelib 3.3.0 appears to be the version shipped with Haxe 3.4.0-rc.1.
I downloaded the latest version of Unity platform-agnostic self-extracting installation script and successfully installed it:
$ sudo sh ./unity-editor-installer-5.4.0p1+20160810.sh
Installer for Unity 5.4.0p1
Press Enter to begin extracting to ./unity-editor-5.4.0p1
Unpacking Unity 5.4.0p1 ...
Extraction complete. Run ./unity-editor-5.4.0p1/Editor/Unity to begin
Then I tried to run the Editor:
$ ./unity-editor-5.4.0p1/Editor/Unity
These two windows appear immediately when the command above is run:
and nothing more happened for the whole night. No error messages, no console output, no log files and no syslog entries. top utility shows that Unity process utilizes one core for 100% of it's CPU time.
I run OpenSUSE 13.2 with up-to-date nVidia graphics drivers. My system also matches all dependencies and requirements listed here, and I didn't see any other instructions except "run the installation script, then run the editor". Unity works OK on Windows with the same hardware.
So my questions are:
How (if possible) to run Unity Editor on non-Ubuntu distributions?
Where can I find error messages (if any) which might clarify the reasons of the issue?
This seems to be a common linux bug.
I can't make any assurances but what worked for me (and what seems to be the most suggested fix on the unity forums) is to do two things:
update or install NPM
create the directory "~/.local/share/unity3d/Packages"
If your npm is up to date, the directory thing seems to be the big to-do (it worked like crackers for me).
If you've got both...well, at least you get the joy of adventure trying to figure out what else could be going against you.
I used the Software Manager in Linux Mint to install Eclipse Platform. It was working yesterday, however, now whenever I run it I get the following error message:
The Eclipse executable launcher was unable to locate its companion shared library.
I tried uninstalling it and then installing it again. Much to my confusion, this did not work. The error message still persists. It implies Eclipse requires a shared dependency that it cannot find. Is there anyway to find out what this is and install it? I've tried 'apt-get dist-upgrade' to update packages but this didn't resolve the issue at hand.
I have been using linux and Eclipse for years, but I would never suggest anyone install Eclipse from the platform repositories for any distribution.
Get your eclipse zips directly from Eclipse.org
Personally, I would just "Google it." (Or, in my case, "DuckDuckGo it.") Put the exact error-message text in double quotes to tell the search-engine that you are looking for the exact phrase.
DDG promptly referred me to this page: http://veeddie.blogspot.com/2010/06/eclipse-executable-launcher-was-unable.html
I'm having a problem with Subclipse, when trying to do anything like committing, updating or viewing history the first time nothing happens, and the second time I try this error show up:
All this used to work just fine but suddenly it stopped working. All the required packages are installed:
The "SVN interface" option in the preferences is empty/greyed out:
I have another Eclipse installation (Java EE) which has the same packages installed and everything is still working fine there.
I've already tried reinstalling all the SVN packages but to no avail. I'm running Eclipse Kepler on Linux Mint 16 Petra, SVN is version 1.7.9.
Any help would be greatly appreciated.
EDIT: I figured out that the other Eclipse installation had different (older) versions of the plugins. After updating these, that installation also stopped working. I suspect that my SVN version (1.7.9) is too old. I see 1.8.x has already been released, how can I install that version in my Linux installation? Running apt-get update/upgrade doesn't do it. I've seen some people talking about running dist-upgrade but that has broken things in the past so I'm very reluctant to do so unless absolutely necessary.
EDIT: I managed to install subversion 1.8.10 using these steps, but to no avail.
I managed to solve the issue my removing SVNKit and installing the "Subversion JavaHL Native Library Adapter" instead. I tried that before but it did work after I had also updated subversion to 1.8.
My MonoTouch install is screwed somehow (MonoDevelop won't even open).
So yesterday I deleted /Developer/MonoTouch off my Mac because that was the only directions I could find for uninstalling it. Today I tried reinstalling both it and MonoDevelop. Both installers ran fine, but I still have the same issue so I went to "uninstall" it again...and that directory doesn't exist this time.
Then I went to install an older version (2.6.7) and that installer tells me that I have a newer version already installed.
So....what do I do?
I am in a very, very bad mood because of all this right now. A months worth of work is now pointless unless I can get this running again.
EDIT
I finally got an older version of MonoTouch to install. Version 2.6.7 that was downloaded off of their site. Now when I run MonoDevelop I get an error that says "MonoDevelop requires the Mono Framework version 2.6.7 or later" and gives me the option to "Cancel" or "Download".
This is the error that I got that started this whole thing. I installed 2.6.7 but it doesn't recognize, and if I install 2.8 it just won't launch (icon bounces 3 times then does nothing, no error, no app).
EDIT 2
The other thing of note is that no matter how many times I install/uninstall/reinstall any version of the Mono Framework, nothing at all shows up in /Developer/MonoTouch.
I don't know how important that is, but considering something used to be there until this problem started I thought it worth mentioning.
Also since this problem started, I can no longer open any .xib files inside of Interface Builder. Whether that means one created in XCode or opening Interface Builder then creating a new View. Interface Builder runs fine, but as soon as I try to open any .xib it crashes with this error report.
I notice it says something about libxml2 in there which WAS installed yesterday and is probably the root cause of this...but I have uninstalled and reinstalled that as well with no luck.
You need to install Mono 2.6.7 or later, please download and install:
http://ftp.novell.com/pub/mono/archive/2.8/macos-10-x86/10/MonoFramework-2.8_10.macos10.novell.x86.dmg