Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#22553 closed defect (worksforme)

TOR 7 does not start on OS X 10.9.5

Reported by: StefanK Owned by: tbb-team
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Critical Keywords:
Cc: mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

After upgrading from 6.5.2 to 7.0, an error message about for-starter crashing displays when starting TOR 7.
Removing and reinstalling TOR 7 from dmg shows same problem.

After removing TOR 7 and reinstalling 6.5.2, this now also fails to start with same error message

Child Tickets

Change History (19)

comment:1 Changed 2 years ago by gk

Component: - Select a componentApplications/Tor Browser
Priority: ImmediateVery High
Severity: BlockerCritical
Status: newneeds_information

What is "for-starter crashing displays"? could you give us the complete error message?

comment:2 Changed 2 years ago by gk

Owner: set to tbb-team
Status: needs_informationassigned

comment:3 Changed 2 years ago by gk

Status: assignedneeds_information

Oh, and does a normal Firefox 52 ESR work on your system?

comment:4 Changed 2 years ago by StefanK

I currently run a regular Firefox 53.0.3 on my Mac. I never had issues when upgrading the regular Firefox.

Last edited 2 years ago by StefanK (previous) (diff)

comment:5 in reply to:  4 Changed 2 years ago by gk

Replying to StefanK:

I currently run a regular Firefox 53.0.3 on my Mac. I never had issues when upgrading the regular Firefox.

That's good to know, thanks. Could you give us the complete error message you get when starting Tor Browser?

Last edited 2 years ago by gk (previous) (diff)

comment:6 Changed 2 years ago by StefanK

Sorry about "for-starter". It seems typos can not be corrected after sending the message.

Anyway, the (german) error message that displays is from a "Tor-Starter" dialog and says:

"Tor wurde unerwartet beendet. Dies kann die Folge eines Fehlers in ihrer "torrc"-Datei sein, ein Fehler in Tor, einem anderen Programm in ihrem System oder fehlerhafte Hardware sein. Bis die Ursache beseitigt wurde und Tor neugestartet wurde, wird der Tor Browser nicht starten."

("Tor quit unexpectedly. This could be caused by an error in your "torrc" file, an error in Tor, another program in your system or faulty hardware. Tor browser will not launch until this issue has been fixed and Tor restarted.")

Last edited 2 years ago by StefanK (previous) (diff)

comment:7 Changed 2 years ago by gk

Thanks. Could you follow the steps in comment:11:ticket:20300 and report the output back in this ticket?
And, assuming you have Tor Browser in your /Applications directory does dragging Tor Browser just to the desktop and starting it from there work for you?

comment:8 Changed 2 years ago by catalyst

I think I've seen a very similar problem during an upgrade to 7.0a4 from 7.0a3. It could be due to Tor Launcher supplying ControlPort or SocksPort options on the tor command line that conflict with a torrc or torrc-defaults from an older Tor Browser. Possibly related to #22283 or #22546.

comment:9 Changed 2 years ago by StefanK

  1. Here is the debug output you requested:

[06-12 17:29:21] TorLauncher INFO: debug output ready
[06-12 17:29:21] TorLauncher INFO: SOCKS port type: TCP
[06-12 17:29:21] TorLauncher INFO: SOCKS host: 127.0.0.1
[06-12 17:29:21] TorLauncher INFO: SOCKS port: 9150
[06-12 17:29:21] TorLauncher DBUG: Starting /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/tor
[06-12 17:29:21] TorLauncher DBUG: --defaults-torrc
[06-12 17:29:21] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/torrc-defaults
[06-12 17:29:21] TorLauncher DBUG: -f
[06-12 17:29:21] TorLauncher DBUG: /Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc
[06-12 17:29:21] TorLauncher DBUG: DataDirectory
[06-12 17:29:21] TorLauncher DBUG: /Users/stefan/Library/Application Support/TorBrowser-Data/Tor
[06-12 17:29:21] TorLauncher DBUG: GeoIPFile
[06-12 17:29:21] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip
[06-12 17:29:21] TorLauncher DBUG: GeoIPv6File
[06-12 17:29:21] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip6
[06-12 17:29:21] TorLauncher DBUG: HashedControlPassword
[06-12 17:29:21] TorLauncher DBUG: 16:40180975919f160b602ee4cb3f6bbf82ad60d4f38ae91d0f7717b15077
[06-12 17:29:21] TorLauncher DBUG: +ControlPort
[06-12 17:29:21] TorLauncher DBUG: 9151
[06-12 17:29:21] TorLauncher DBUG: +
SocksPort
[06-12 17:29:21] TorLauncher DBUG: 127.0.0.1:9150 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
[06-12 17:29:21] TorLauncher DBUG: OwningControllerProcess
[06-12 17:29:21] TorLauncher DBUG: 63198
Jun 12 19:29:21.751 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) running on Darwin with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.5.
Jun 12 19:29:21.752 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 12 19:29:21.753 [notice] Read configuration file "/Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/torrc-defaults".
Jun 12 19:29:21.754 [notice] Read configuration file "/Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc".
Jun 12 19:29:21.759 [warn] Failed to parse/validate config: Unknown option '
ControlPort'. Failing.
Jun 12 19:29:21.760 [err] Reading config failed--see warnings above.
[06-12 17:29:21] TorLauncher DBUG: Opening control connection to 127.0.0.1:9151
[06-12 17:29:21] TorLauncher DBUG: Sending Tor command: AUTHENTICATE 274c59226136606a35525b5c5d342865
[06-12 17:29:21] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REFUSED) [nsIBinaryOutputStream.writeBytes]" nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)" location: "JS frame :: jar:file:///Users/stefan/Library/Application%20Support/TorBrowser-Data/Browser/v6kgw0uh.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._sendCommand :: line 886" data: no]
[06-12 17:29:21] TorLauncher NOTE: Tor wurde unerwartet beendet. Dies kann die Folge eines Fehlers in ihrer "torrc"-Datei sein, ein Fehler in Tor, einem anderen Programm in ihrem System oder fehlerhafte Hardware sein. Bis die Ursache beseitigt wurde und Tor neugestartet wurde, wird der Tor Browser nicht starten.

  1. After moving Tor Browser 6.5.2 to the desktop, I could start it without problems. Also, updating to 7.0 worked!

comment:10 Changed 2 years ago by gk

Cc: mcs added

comment:11 Changed 2 years ago by mcs

Thank you for posting the debug output. The reason Tor Browser works fine when run from the desktop is because new configuration is used in that case.

This line from your log indicates that your other torrc file is now invalid:

Jun 12 19:29:21.759 [warn] Failed to parse/validate config: Unknown option 'ControlPort'. Failing.

My best guess is that Tor Launcher failed to clean up your torrc file correctly after the upgrade to 7.0 (see #20761 for the backstory).

Can you please attach a copy of the file /Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc to this ticket? And can you also post the contents of any other files whose names begin with torrc that are located in that same folder? Doing so should help us debug this problem so we can avoid it happening again.

comment:12 in reply to:  11 Changed 2 years ago by gk

Replying to mcs:

Can you please attach a copy of the file /Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc to this ticket? And can you also post the contents of any other files whose names begin with torrc that are located in that same folder? Doing so should help us debug this problem so we can avoid it happening again.

That is a good idea, yes, please. However, I think the bug as shown in the log can be easily explained: The profile directory contains 7.0 related data (including the extensions we shipped with it) and after 6.5.2 got installed over 7.0 tor is complaining that it does not know what to do with __ControlPort (Yes, with two underscores, don't get fooled by Trac formatting in the browser). And, sure, that's totally expected as tor 0.2.9.10 does not know what that is. Hence the error.

StefanK: Could you install Tor Browser 7.0 over 6.5.2 in your /Applications directory and do the things asked in comment:7 again? That would be most helpful, thanks.

comment:13 Changed 2 years ago by StefanK

mcs: which exact steps should I take installing 7.0 over 6.5.2?

Should I remove both the 7.0 app and "/Users/stefan/Library/Application Support/TorBrowser-Data/" ?

After installing 6.5.2, should I do an upgrade to 7.0 from the application itself or install from the dmg?

comment:14 in reply to:  13 Changed 2 years ago by gk

Replying to StefanK:

mcs: which exact steps should I take installing 7.0 over 6.5.2?

Should I remove both the 7.0 app and "/Users/stefan/Library/Application Support/TorBrowser-Data/" ?

After installing 6.5.2, should I do an upgrade to 7.0 from the application itself or install from the dmg?

Sorry for the confusion. The first thing that would be helpful is:

Can you please attach a copy of the file /Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc to this ticket? And can you also post the contents of any other files whose names begin with torrc that are located in that same folder?

The other thing after having done the first one above is:
Please do again what you described in the description: getting rid of Tor Browser in your /Applications directory and reinstalling it (this time Tor Browser 7 from our download page). Then we'd like to see a similar log to the one you added in comment:9, thanks.

comment:15 Changed 2 years ago by StefanK

I get an error from Trac when trying to attach the torrc file (tried with two different browsers).

The content of the file is:

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

DataDirectory /Users/stefan/Library/Application Support/TorBrowser-Data/Tor
GeoIPFile /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip
GeoIPv6File /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip6
HiddenServiceStatistics 0

After removing both TorBrowser and TorBrowserData folders from the Desktop and then installing Tor 7 from dmg to /Applications, Tor now starts without error.

The new debug output is:
[06-13 13:26:03] TorLauncher INFO: debug output ready
[06-13 13:26:03] TorLauncher INFO: SOCKS port type: TCP
[06-13 13:26:03] TorLauncher INFO: SOCKS host: 127.0.0.1
[06-13 13:26:03] TorLauncher INFO: SOCKS port: 9150
[06-13 13:26:03] TorLauncher DBUG: Starting /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/tor
[06-13 13:26:03] TorLauncher DBUG: --defaults-torrc
[06-13 13:26:03] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/torrc-defaults
[06-13 13:26:03] TorLauncher DBUG: -f
[06-13 13:26:03] TorLauncher DBUG: /Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc
[06-13 13:26:03] TorLauncher DBUG: DataDirectory
[06-13 13:26:03] TorLauncher DBUG: /Users/stefan/Library/Application Support/TorBrowser-Data/Tor
[06-13 13:26:03] TorLauncher DBUG: GeoIPFile
[06-13 13:26:03] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip
[06-13 13:26:03] TorLauncher DBUG: GeoIPv6File
[06-13 13:26:03] TorLauncher DBUG: /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip6
[06-13 13:26:03] TorLauncher DBUG: HashedControlPassword
[06-13 13:26:03] TorLauncher DBUG: 16:8904df0bec2ef25360b5e24c5885d4529821334f80293bf16b63dabd0b
[06-13 13:26:03] TorLauncher DBUG: +ControlPort
[06-13 13:26:03] TorLauncher DBUG: 9151
[06-13 13:26:03] TorLauncher DBUG: +
SocksPort
[06-13 13:26:03] TorLauncher DBUG: 127.0.0.1:9150 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
[06-13 13:26:03] TorLauncher DBUG: OwningControllerProcess
[06-13 13:26:03] TorLauncher DBUG: 21657
Jun 13 15:26:03.462 [notice] Tor 0.3.0.7 (git-cfd9c1bdc0582656) running on Darwin with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.5.
Jun 13 15:26:03.463 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 13 15:26:03.465 [notice] Read configuration file "/Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/torrc-defaults".
Jun 13 15:26:03.465 [notice] Read configuration file "/Users/stefan/Library/Application Support/TorBrowser-Data/Tor/torrc".
Jun 13 15:26:03.474 [notice] Opening Socks listener on 127.0.0.1:9150
Jun 13 15:26:03.474 [notice] Opening Control listener on 127.0.0.1:9151
Jun 13 15:26:03.000 [notice] Parsing GEOIP IPv4 file /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip.
[06-13 13:26:03] TorLauncher DBUG: Opening control connection to 127.0.0.1:9151
[06-13 13:26:03] TorLauncher DBUG: Sending Tor command: AUTHENTICATE 6b45212e336b62224123634276455957
Jun 13 15:26:03.000 [notice] Parsing GEOIP IPv6 file /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip6.
Jun 13 15:26:03.000 [notice] Bootstrapped 0%: Starting
Jun 13 15:26:04.000 [notice] Starting with guard context "default"
Jun 13 15:26:04.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 13 15:26:04.000 [notice] New control connection opened from 127.0.0.1.
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
[06-13 13:26:04] TorLauncher DBUG: Sending Tor command: TAKEOWNERSHIP
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
[06-13 13:26:04] TorLauncher DBUG: Sending Tor command: RESETCONF
OwningControllerProcess
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
[06-13 13:26:04] TorLauncher DBUG: Opening control connection to 127.0.0.1:9151
[06-13 13:26:04] TorLauncher DBUG: Sending Tor command: AUTHENTICATE 6b45212e336b62224123634276455957
Jun 13 15:26:04.000 [notice] New control connection opened from 127.0.0.1.
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
[06-13 13:26:04] TorLauncher DBUG: Sending Tor command: SETEVENTS STATUS_CLIENT NOTICE WARN ERR
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
[06-13 13:26:04] TorLauncher DBUG: Sending Tor command: GETINFO status/bootstrap-phase
[06-13 13:26:04] TorLauncher DBUG: Command response: 250-status/bootstrap-phase=NOTICE BOOTSTRAP PROGRESS=80 TAG=conn_or SUMMARY="Connecting to the Tor network"
[06-13 13:26:04] TorLauncher DBUG: Command response: 250 OK
Jun 13 15:26:04.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
[06-13 13:26:04] TorLauncher DBUG: Event response: 650 NOTICE Bootstrapped 85%: Finishing handshake with first hop
[06-13 13:26:04] TorLauncher DBUG: Event response: 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=85 TAG=handshake_or SUMMARY="Finishing handshake with first hop"
Jun 13 15:26:05.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
[06-13 13:26:05] TorLauncher DBUG: Event response: 650 NOTICE Bootstrapped 90%: Establishing a Tor circuit
[06-13 13:26:05] TorLauncher DBUG: Event response: 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=90 TAG=circuit_create SUMMARY="Establishing a Tor circuit"
Jun 13 15:26:06.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jun 13 15:26:06.000 [notice] Bootstrapped 100%: Done
[06-13 13:26:06] TorLauncher DBUG: Event response: 650 NOTICE Tor has successfully opened a circuit. Looks like client functionality is working.
[06-13 13:26:06] TorLauncher DBUG: Event response: 650 NOTICE Bootstrapped 100%: Done
[06-13 13:26:06] TorLauncher DBUG: Event response: 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
[06-13 13:26:06] TorLauncher DBUG: Event response: 650 STATUS_CLIENT NOTICE CIRCUIT_ESTABLISHED
[06-13 13:26:06] TorLauncher INFO: NOTICE CIRCUIT_ESTABLISHED
Jun 13 15:26:08.000 [notice] New control connection opened from 127.0.0.1.
[06-13 13:26:08] TorLauncher DBUG: Event response: 650 NOTICE New control connection opened from 127.0.0.1.
Jun 13 15:26:08.000 [notice] New control connection opened from 127.0.0.1.
[06-13 13:26:08] TorLauncher DBUG: Event response: 650 NOTICE New control connection opened from 127.0.0.1.
2017-06-13 13:26:08.599 plugin-container[21661:1940138] * CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x953f, name = 'com.apple.tsm.portname'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2017-06-13 13:26:08.602 plugin-container[21661:1940138]
* CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x9823, name = 'com.apple.CFPasteboardClient'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2017-06-13 13:26:08.602 plugin-container[21661:1940138] void CFPasteboardSetup() : Failed to allocate communication port for com.apple.CFPasteboardClient; this is likely due to sandbox restrictions

comment:16 in reply to:  15 Changed 2 years ago by gk

Replying to StefanK:

I get an error from Trac when trying to attach the torrc file (tried with two different browsers).

The content of the file is:

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

DataDirectory /Users/stefan/Library/Application Support/TorBrowser-Data/Tor
GeoIPFile /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip
GeoIPv6File /Applications/TorBrowser.app/Contents/Resources/TorBrowser/Tor/geoip6
HiddenServiceStatistics 0

After removing both TorBrowser and TorBrowserData folders from the Desktop and then installing Tor 7 from dmg to /Applications, Tor now starts without error.

Thanks for helping. So, everything is working for you now and you don't have a way to reproduce your initial issue?

comment:17 Changed 2 years ago by StefanK

1) Yes, TorBrowser 7 is working now

2) Regarding reproducing the issue, this would mean completely erasing all traces of TorBrowser from OS X, installing 6.5.2 and then doing an in-app update to 7.0. This procedure was not covered in the above troubleshooting steps, and I'd rather not do that unless it is absolutely necessary.

comment:18 Changed 2 years ago by gk

Resolution: worksforme
Status: needs_informationclosed

No, that's fine, thanks for your help.

comment:19 Changed 2 years ago by StefanK

FYI, I just ran the in-app upgrade to 7.0.1 without problems.

Note: See TracTickets for help on using tickets.