Problem launching android AVM/SDK gui using the tools/android executable in the android SDK. Ubuntu 10.04, i686

Question

Hi I just installed the android SDK along with Eclipse 3.5 on my i686 Thinkpad T60 running Ubuntu 10.04 (Lucid). (Eclipse was installed via synaptic, i.e. a package from the repository.) I installed the eclipse add on and everything on the Eclipse end seems fine. I also put the android-sdk tools directory on my user PATH. Now launching tools/android without any arguments is supposed to bring up the SDK and AVD manager GUI, but instead I get the following error:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-gtk-3550 or swt-gtk in swt.library.path, java.library.path or the jar file
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.C.<clinit>(Unknown Source)
    at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
    at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
    at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)
    at com.android.sdkmanager.Main.showMainWindow(Main.java:265)
    at com.android.sdkmanager.Main.doAction(Main.java:249)
    at com.android.sdkmanager.Main.run(Main.java:94)
    at com.android.sdkmanager.Main.main(Main.java:83)

The strange thing is I definitely have all the prerequisites installed, sun-java6-jdk, and open-java6-jdk and have tried switching between them. Also if I look in synaptic I have libswt-gtk-3.5java installed. Also he AVM/SDK manager launches fine when I launch it with eclipse.

(You may wonder why i care, but I like working from the command line, and considering using emacs as my IDE rather than Eclipse.)

If anyone knows how i can fix this please let me know.

Answer 1

(copied from Ubuntuforums http://ubuntuforums.org/showthread.php?t=1540054)

I had the same issue 12 months on. I discovered that it was because I had made the /tmp directory "noexec" as soon as I made it executable, we were fine.

sudo mount -o remount,exec /tmp

Hope this helps someone.

Answer 2

Additionally to what the user Bart well and correctly said I suggest to pay attention into the tip bellow:

Advanced linux users or geeks more often will face this issue. A "tweak" (usually to get more speed) applied in /etc/fstab making /tmp as noexec will cause this problem. Just open fstab and modify the entry as follow bellow:

sudo gedit /etc/fstab

If you have something like this just comment the line or modify the content:

tmpfs /tmp tmpfs defaults,noexec,nodev,nosuid 0 0

TO:

tmpfs /tmp tmpfs defaults,nodev,nosuid 0 0

Answer 3

Have a look at

android <command> --no-ui

This doesn't require SWT/GTK at all.