[tor-bugs] #4805 [Vidalia]: Vidalia 0.2.15 update messed up with TOR config

[Tor Bug Tracker & Wiki]

#4805: Vidalia 0.2.15 update messed up with TOR config
---------------------------+------------------------------------------------
 Reporter:  ggallozz       |          Owner:  chiiph         
     Type:  defect         |         Status:  new            
 Priority:  normal         |      Milestone:                 
Component:  Vidalia        |        Version:  Vidalia: 0.2.15
 Keywords:  update 0.2.15  |         Parent:                 
   Points:                 |   Actualpoints:                 
---------------------------+------------------------------------------------

Comment(by travisp):

 I can confirm this bug. At some point in the last month or two, my
 tor/vidalia configuration stopped working after an upgrade from the
 repository. I am on Ubuntu 11.10 64-bit, with Tor version 0.2.2.35 and
 vidalia 0.2.15. I installed them using my package manager from the
 http://deb.torproject.org/torproject.org repository. They both previously
 worked fine together.

 Error log:
 {{{
 Jan 02 14:04:56.192 [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 02 14:04:56.192 [Notice] Initialized libevent version 2.0.12-stable
 using method epoll. Good.
 Jan 02 14:04:56.192 [Notice] Opening Socks listener on 127.0.0.1:9050
 Jan 02 14:04:56.192 [Warning] /var/run/tor is not owned by this user
 (travis, 1000) but by debian-tor (114). Perhaps you are running Tor as the
 wrong user?
 Jan 02 14:04:56.192 [Warning] Before Tor can create a control socket in
 "/var/run/tor/control.authcookie", 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 02 14:04:56.192 [Notice] Closing partially-constructed listener Socks
 listener on 127.0.0.1:9050
 Jan 02 14:04:56.192 [Warning] Failed to parse/validate config: Failed to
 bind one of the listener ports.
 Jan 02 14:04:56.192 [Error] Reading config failed--see warnings above.
 }}}

 Please note that I did not have an unusual configuration prior to this
 when everything was working, and that they simply stopped working after
 the new versions were upgraded by the package manager.

 A discussion with another user on IRC brought up the claim that the
 upgrade changed vidalia's configuration to use a control socket in
 /var/run instead of the control port (which also broke their install).
 This seemed to be the case in my configuration as well.

 My working solution:

 1. Open vidalia settings
 2. Click advanced
 3. Click Use TCP connect (ControlPort) instead of unix domain socket.
 4. Click ok and completely exit vidalia and reload

 After these steps, Vidalia/tor worked together again.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4805#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online