Whenever I start Tor in Ubuntu 13.04, the Vidalia Control Panel opens, loads up and displays a status of "Connected to the Tor network!". However, the tor-infused firefox, does not pop up like it should.
Tor log:
jul. 04 02:09:11.859 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Linux.
jul. 04 02:09:11.860 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
jul. 04 02:09:11.861 [Notice] Read configuration file "/home/joren/.tor-browser/App/../Data/Tor/torrc".
jul. 04 02:09:11.872 [Notice] Initialized libevent version 2.0.21-stable using method epoll (with changelist). Good.
jul. 04 02:09:11.873 [Notice] Opening Socks listener on 127.0.0.1:9150
jul. 04 02:09:11.873 [Notice] Opening Control listener on 127.0.0.1:9151
jul. 04 02:09:11.937 [Notice] Parsing GEOIP file ./Data/Tor/geoip.
jul. 04 02:09:12.178 [Notice] No AES engine found; using AES_* functions.
jul. 04 02:09:12.178 [Notice] This OpenSSL has a good implementation of counter mode; using it.
jul. 04 02:09:12.235 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
jul. 04 02:09:12.740 [Notice] Reloaded microdescriptor cache. Found 8497 descriptors.
jul. 04 02:09:12.740 [Notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
jul. 04 02:09:13.758 [Notice] Bootstrapped 5%: Connecting to directory server.
jul. 04 02:09:13.761 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 1 circuits open. I've sent 0 kB and received 0 kB.
jul. 04 02:09:13.908 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
jul. 04 02:09:14.252 [Notice] Bootstrapped 15%: Establishing an encrypted directory connection.
jul. 04 02:09:14.507 [Notice] Bootstrapped 20%: Asking for networkstatus consensus.
jul. 04 02:09:14.615 [Notice] Bootstrapped 25%: Loading networkstatus consensus.
jul. 04 02:09:16.446 [Notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
jul. 04 02:09:16.447 [Notice] Bootstrapped 45%: Asking for relay descriptors.
jul. 04 02:09:16.448 [Notice] I learned some more directory information, but not enough to build a circuit: We have only 113/3851 usable microdescriptors.
jul. 04 02:09:17.755 [Notice] We now have enough directory information to build circuits.
jul. 04 02:09:17.755 [Notice] Bootstrapped 80%: Connecting to the Tor network.
jul. 04 02:09:17.810 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
jul. 04 02:09:17.818 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
jul. 04 02:09:18.156 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
jul. 04 02:09:18.157 [Notice] Bootstrapped 100%: Done.
How do I proceed solving this issue?
Best Answer
Tor Browser 10 fixes Bug 33906: Fix Tor-Launcher issues for Firefox 75.
Tor Browser (torbrowser-launcher) is available in the default Ubuntu repositories in Ubuntu 16.04 and later. torbrowser-launcher handles downloading the most recent version of Tor Browser Bundle for you, in your language and for your architecture. After installing Tor Browser, it can be launched by searching for tor in the Dash and clicking the Tor Browser icon. The Tor Browser Launcher Settings app is also installed along with Tor Browser.
Unfortunately the Tor Browser developers change their signing key that is used to install Tor Browser at periodic intervals which makes the torbrowser-launcher package from the default Ubuntu repositories not work because it is not as up-to-date as the current version of Tor Browser.
These are the instructions from the official Tor Browser User Manual in case the Ubuntu torbrowser-launcher package hasn't updated the gpg key that is required to install Tor Browser. When I updated the Tor Browser Developers signing key I noticed that the key that I updated will expire in less than one year.
Navigate to the Tor Browser download page.
Download the GNU/Linux .tar.xz file
(Recommended) Verify the file's signature. The steps for verifying the file's signature are shown below.
When the download is complete, extract the archive with the command
tar -xf [TB archive]or with the Archive Manager.Navigate to the newly extracted Tor Browser directory. Right click on start-tor-browser.desktop, open Properties and change the permission to Allow executing file as program by clicking the checkbox. Double-click the icon to start up Tor Browser for the first time.
Alternatively, from inside the Tor Browser directory, you can also start from the command line by running:
How to verify Tor Browser's signature
Fetching the Tor Developers key
The Tor Browser team signs Tor Browser releases. Import the Tor Browser Developers signing key (0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290):
This should show you something like:
After importing the key, you can save it to a file (identifying it by fingerprint here):
Verifying the signature
To verify the signature of the package you downloaded, you will need to download the corresponding ".asc" signature file as well as the installer file itself, and verify it with a command that asks GnuPG to verify the file that you downloaded.
The example below assumes that you downloaded these two files to your Downloads folder.
The result of the command should produce something like this: