Adb not working on Ubuntu 64 - command not found

Question

Update

Having done some more experiments, I have to completely reformulate my question, since my terminal deceived me. It just didn't show an error message when I released sudo./adb .

If I connect to the ANDOID_SDK / platform-tools directory and run ./adb , I get:

command not found: ./adb 

Here's the output of ls -l adb in the same directory:

 -rwxrwxr-x 1 myuser myuser 159620 2011-12-20 19:30 adb 

The run that adb gives me:

 ./adb 

The same thing happens for all other binary executables in this directory, such as aapt, aidl, dexdump, etc.

I could just imagine that this has something to do with me trying to run it on 64-bit Ubuntu, but the ELF header or something like that is not recognized. However, the android tool in the ANDOID_SDK / tools works fine (except that adb failed to execute after loading new packages).

Really weird ...

Original question

I downloaded the latest version of the Android SDK. If I try to run adb as a regular user, I get the command "not found". I have to run it as "sudo./adb" and it works. Why is this and how can I fix it? I am running Ubuntu 64 11.10.

I used the SDK for older versions of Ubuntu, and there I could run it as a regular user without any problems. Any ideas?

Answer 1

I have found a solution. I explored again if I really have ia32-libs installed. At first glance, it looked great in ability. However, at first glance, I noticed that the ia32-libs package was installed, but not all the dependencies. I could not resolve this with aptitude, but instead I had to remove ia32-libs using the KDE package manager and install it again. Now all the missing 88 dependencies have been installed. adb now works fine.

I am not 100% sure why aptitude failed here, but I suspect that she also suffers from this installation error: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/831768 I also There are duplicate entries in aptitude for all entries.

Answer 2

Add platform tools to the environment variable, for this

Add the following line to your home folder in the /home/yourUserName/.bashrc file.

export PATH = "your / path / android-sdk-linux / platform-tools /: $ {PATH}"

Answer 3

Run "chown" in the sdk android folder to make your account the owner of the folder. It looks like it belongs to root now. I cannot remember the syntax, but there will be many examples on the Internet.