Opened 5 years ago

Last modified 18 months ago

#12501 new defect

"Tor unexpectedly exited" if there is a wrong line in torrc

Reported by: Sherief Owned by: brade
Priority: Medium Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords:
Cc: mcs Actual Points:
Parent ID: #10059 Points:
Reviewer: Sponsor:

Description

I decided to add a new fte bridge and by chance I had torrc open in my text editor then entered "bridg fte ip:port fingerprint". (I shouldn't have done that.)

Then I started Tor Launcher and it kept spitting out "Tor Unexpectedly exited". So I did a ./start-tor-browser

Jun 30 22:49:58.033 [warn] Failed to parse/validate config: Unknown option 'Bridg'.  Failing.
Jun 30 22:49:58.033 [err] Reading config failed--see warnings above.

Wouldn't it be better if Tor Launcher reported back the above messages? I would've never knew my error if I were using Windows.

Also, here's a part of my conversation with arma:

<arma4> what is the bad bridge line? i assume tor does give an explanation.
<sherief> I would've never knew what's wrong without ./start-tor-browser
<sherief> "bridg" missing an "e"
<sherief> :)
<sherief> bridg transportType IP:Port fingerprint
<arma4> expands to bridgeauthoritativedir
<arma4> can you file a ticket, that bridg should expand to bridge?
<arma4>   V(BridgeAuthoritativeDir,      BOOL,     "0"),
<arma4>   VAR("Bridge",                  LINELIST, Bridges,    NULL),
<arma4> i think we just reverse the order of these two lines and it's done
<arma4> doesn't resolve your general issue, but resolves this specific one

Child Tickets

Change History (2)

comment:1 Changed 5 years ago by mcs

Parent ID: #10059

Indeed, Tor Launcher should show you these messages. Unfortunately, they occur before a control connection can be opened, which means currently Tor Launcher does not see them. See #10059.

comment:2 Changed 18 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.