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 th

Answer 1

If you want to launch sdk-manager via commandline, another option is, try running:

> sudo android sdk

This would run in admin mode giving you required permissions

Answer 2

Just delete contents of tmp dir.

sudo rm -rf /tmp/*

Try to launch android sdk manager afterwards. It worked for me.

Answer 3

i also got this problem. I solved it by changing the ownership of the android sdk home directory (that i installed in '/opt') to me. This was done with something like:

sudo chown -R <username> /opt/android-sdk-linux 

And it worked fine !

Answer 4

This is an old question, but I want to propose a less 'drastic' answer...

If you don't want to change your file-system mount, an alternative is that you can change the android tools startup script to explicitly specify the temporary directory that Java should use.

e.g. in the android-studio/sdk/tools directory, right at the end of the android script file is the command that executes java:

exec "$java_cmd" \
    -Djava.io.tmpdir=/home/me/android-studio/.tmp \
    -Xmx256M $os_opts $java_debug \
    -Dcom.android.sdkmanager.toolsdir="$progdir" \
    -classpath "$jarpath:$swtpath/swt.jar" \
    com.android.sdkmanager.Main "$@"

In this example I use "/home/me/android-studio/.tmp" but of course you change that to whatever you want.

Unfortunately this change will get overwritten if you update your Android tools so you would have to reapply it each time you update. You could instead export it in your profile as a global environment property (for all Java applications) instead of editing this script.

Answer 5

Have a look at

android <command> --no-ui

This doesn't require SWT/GTK at all.

Answer 6

(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.