Tor cannot be found in buntu

I tried running Tor, but a message comes up saying
Vidalia detected that the Tor software exited unexpectedly.
Please check the message log for recent warning or error messages.

The advanced message log:

Jan 07 13:05:38.027 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Jan 07 13:05:38.030 [Notice] We were compiled with headers from version 1.4.13-stable of Libevent, but we're using a Libevent library that says it's version 1.4.14b-stable.
Jan 07 13:05:38.030 [Notice] Initialized libevent version 1.4.14b-stable using method epoll. Good.
Jan 07 13:05:38.031 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 07 13:05:38.031 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jan 07 13:05:38.034 [Warning] /var/run/tor is not owned by this user (dale, 1000) but by debian-tor (115). Perhaps you are running Tor as the wrong user?
Jan 07 13:05:38.035 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Jan 07 13:05:38.035 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jan 07 13:05:38.035 [Error] Reading config failed--see warnings above.
Jan 07 13:05:45.972 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Jan 07 13:05:45.978 [Notice] We were compiled with headers from version 1.4.13-stable of Libevent, but we're using a Libevent library that says it's version 1.4.14b-stable.
Jan 07 13:05:45.978 [Notice] Initialized libevent version 1.4.14b-stable using method epoll. Good.
Jan 07 13:05:45.978 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 07 13:05:45.978 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jan 07 13:05:45.984 [Warning] /var/run/tor is not owned by this user (dale, 1000) but by debian-tor (115). Perhaps you are running Tor as the wrong user?
Jan 07 13:05:45.985 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Jan 07 13:05:45.985 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jan 07 13:05:45.985 [Error] Reading config failed--see warnings above.
Jan 07 13:06:13.649 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Jan 07 13:06:13.650 [Notice] We were compiled with headers from version 1.4.13-stable of Libevent, but we're using a Libevent library that says it's version 1.4.14b-stable.
Jan 07 13:06:13.650 [Notice] Initialized libevent version 1.4.14b-stable using method epoll. Good.
Jan 07 13:06:13.651 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 07 13:06:13.651 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jan 07 13:06:13.651 [Warning] /var/run/tor is not owned by this user (dale, 1000) but by debian-tor (115). Perhaps you are running Tor as the wrong user?
Jan 07 13:06:13.651 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Jan 07 13:06:13.651 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jan 07 13:06:13.652 [Error] Reading config failed--see warnings above.
Jan 07 13:09:21.401 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Jan 07 13:09:21.404 [Notice] We were compiled with headers from version 1.4.13-stable of Libevent, but we're using a Libevent library that says it's version 1.4.14b-stable.
Jan 07 13:09:21.407 [Notice] Initialized libevent version 1.4.14b-stable using method epoll. Good.
Jan 07 13:09:21.407 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 07 13:09:21.408 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jan 07 13:09:21.408 [Warning] /var/run/tor is not owned by this user (dale, 1000) but by debian-tor (115). Perhaps you are running Tor as the wrong user?
Jan 07 13:09:21.409 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Jan 07 13:09:21.409 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jan 07 13:09:21.409 [Error] Reading config failed--see warnings above.