Opened 3 years ago

Closed 3 years ago

#24270 closed defect (fixed)

Sandboxed Tor Browser - No downloads for architecture: linux64

Reported by: correcthrsbatterystpl Owned by: yawning
Priority: Medium Milestone:
Component: Archived/Tor Browser Sandbox Version:
Severity: Normal Keywords:
Cc: boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:



I'm trying to install the Tor browser on a 64-bit Debian system. To do so, I used the commands:
$ wget -c
$ unzip
$ cd sandbox
$ ./sandboxed-tor-browser
I then selected "release" as channel and "en_US" as locale, and clicked "OK". A message "Failed to install: no downloads for architecture: linux64" appeared in a message box and the installation exited. The terminal log produced the following output:

2017/11/14 21:12:28 install: Starting.
2017/11/14 21:12:28 install: Checking available downloads.
2017/11/14 21:12:28 install: Metadata URL:
2017/11/14 21:12:32 install: Failing with error: no downloads for architecture: linux64
2017/11/14 21:12:45 fatal error in the user interface: no downloads for architecture: linux64

I have tried asking in IRC. Nobody was able to work out the problem, so Sebastian recommended that I submit a ticket.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by gk

Cc: boklm added

comment:2 Changed 3 years ago by yawning

Cc: boklm removed

There is absolutely nothing I can do when something went wrong in the release process and the metadata file that the downloader uses to figure out what to fetch is badly malformed.


For reference the old valid file (to get an idea of what the code expects) is at:

Last edited 3 years ago by yawning (previous) (diff)

comment:3 Changed 3 years ago by yawning

Cc: boklm added

Whoops, commenting removed the CC, sorry about the noise.

comment:4 Changed 3 years ago by yawning

Well, not "absolutely nothing" because this falls under the general scope of #20792, but that's not something I see myself actively working on in the short to medium term future.

I'll hold off on closing this as a dupe this till the metadata file is fixed by one of the browser people, because that's the best short term course of action.

comment:5 Changed 3 years ago by boklm

Resolution: fixed
Status: newclosed

This should be fixed now. This was an error when releasing version 7.0.9. As this was a release for some architectures only, this file needed to be edited manually.

Note: See TracTickets for help on using tickets.