[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18947 [Applications/Tor Browser]: 6.0a5 is not starting on OS X if put into /Applications
#18947: 6.0a5 is not starting on OS X if put into /Applications
--------------------------------------+-----------------------------------
Reporter: gk | Owner: mcs
Type: defect | Status: needs_information
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Critical | Resolution:
Keywords: TorBrowserTeam201605 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+-----------------------------------
Comment (by nickm):
Replying to [comment:7 mcs]:
> Replying to [comment:6 cypherpunks]:
> > Your old torrc seems to have a Log option whose path wasn't migrated
to the new bundle data location. It should probably point to
`/Users/nickm/Library/Application Support/TorBrowser-Data/Tor/info.log`.
Maybe this wasn't a Tor Browser profile problem after all?
>
> It could be argued that this is a migration problem. We could add code
to Tor Browser that tries to fix up paths inside torrc during profile
migration. But that seems like a bad idea since Tor Browser currently has
no knowledge of how to parse a torrc file, including which config file
directives accept paths.
>
> In an ideal world we would capture stderr inside Tor Launcher (which
would have made the problem obvious at least). This also tells me that
fixing #10059 by providing a mechanism to ask for log messages via the
control port is perhaps not the best solution; in this case, tor exited to
soon for such a solution to be effective.
Getting the stdout/stderr would have been helpful in this case, yeah.
Also I wonder if somewhere down the line we might have some way in
particular for Tor to report this kind of error so the Launcher can say
something like, "Tor found a problem with your configuration. It said,
"[message here]". Retry with a fresh configuration?"
> One thing still confuses me about this ticket though. In the
description, gk said:
> > Running "tor.real" from the command line is starting it fine.
> Maybe a different torrc was used for that test?
I think that no torrc was used for that test. :)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18947#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs