Opened 7 years ago
Closed 7 years ago
#6307 closed defect (fixed)
Vidalia 0.2.19 updated, can't start TOR
| Reported by: | ggallozz | Owned by: | chiiph |
|---|---|---|---|
| Priority: | Medium | Milestone: | Tor: unspecified |
| Component: | Archived/Vidalia | Version: | Tor: 0.2.3.18-rc |
| Severity: | Keywords: | Vidalia Tor 0.2.18-rc | |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
After upgrade to
-Vidalia 2.19, and
-TOR v0.2.3.18-rc (git-a2015428e4698ff9)
-using Ubuntu 10.10
can't launch TOR from Vidalia (which's used to do it automatically for TOR and POLIPO)
Message:
"Vidalia detected that the Tor software exited unexpectedly.
Please check the message log for recent warning or error messages"
Otherwhile, I can launch TOR manually in a console, but it read configuration file "/etc/tor/torrc" instead from "~/.Vidalia/torrc" which is the configured in Vidalia settings.
Nothing is written in the log, even if all loggin flags are checked.
Child Tickets
Attachments (1)
Change History (3)
Changed 7 years ago by
| Attachment: | ggnotes.txt added |
|---|
comment:1 Changed 7 years ago by
Resolved changing TOR line command in Vidalia settings General tab:
"/usr/sbin/tor"
previously was just "tor"
Still Remains the question: why upgrades still mess up with something ?
here you can find TOR's log
comment:2 Changed 7 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This issue is related to how Vidalia handles certain configuration values. In your case, you had "tor" as the binary, which Vidalia interprets as a relative path so it prepends the absolute path of Vidalia's binary to it. This change was done because of an inconsistency in the path handling in the multiple platforms, I'm sorry this troubled you but this shouldn't change any time soon unless we have a really good reason for it.
Tor console messages