I find that opening the Mac Tor Browser Bundle does not always open Firefox, often only Vidalia is opened. I have to completely close Vidalia and re-open it to get a useable Tor Browser. This seems random. Any time i close/re-open it, I can not predict rather the browser will open or not.
Sometimes I have to close and re-open it 3 or more times for the browser to show. This happens even when no other programs are running. I have also independently confirmed this bug through a friend. I am sure it is not a problem specific to my system. This has been a problem since the first Mac release, but I have neglected to file a bug until now. Apologies if this is a known issue, I could not find a bug that matched this through my searches. I am using: OSX Snow Leopard 10.6.4 w/ all current updates Macbook Pro 2010 Tor Browser Bundle for Mac version 1.0.4 en-US (affects ALL prior versions of the Mac bundle).
Mttp - do you have any information about whether this applies to a specific architecture, or does it happen with both i386 and x8664? Packardbell - if you run./start-tor-browser -debug from the terminal it should give you a mighty debug log with information about Firefox. There may be some personal information (mostly paths) that you don't want public, and if that's the case feel free to scrub it before publishing here, or you can send it to me privately via encrypted email (erinn@, key 63FEE659, the one that signs the bundles). Ok, here's a scrubbed and edited log from a failed start, original is 6.5Mb. Vidalia started and connected to Tor network but Tor Browser failed.
Muutoshistoria Ohjelmalle Tor Browser Bundle For Mac Free
Linux Mint Debian, kernel 3.2.0-4-amd64. Random error, every third time it'll start normally. Jun 14!14:54:39.669 notice Resetting UI translation to English default.
Muuto Historia Ohjelmat Tor Browser Bundle For Mac
Jun 14!14:54:39.669 info Removing all currently installed UI translator objects. Jun 14!14:54:39.671 notice Vidalia 0.2.21 using Qt 4.8.1 Jun 14!14:54:40.144 info Using Tor's GeoIP database for country-level relay mapping. Jun 14!14:54:40.668 notice Tor status changed from 'Unset' to 'Stopped'. Jun 14!14:54:40.812 notice Tor status changed from 'Stopped' to 'Starting'. Jun 14!14:54:40.982 debug QtDebugMsg: torcontrol: Starting Tor using '/home/./././App/./tor -f /home/./App/./Data/Tor/torrc DataDirectory /home/./Data/Tor ControlPort 9151 OwningControllerProcess 4955 HashedControlPassword!16:CE10441B1C3CC7F660C2348C694DB92F03BCEC716E1BC33B65DEC91DA1' Jun 14!14:54:41.122 notice Tor status changed from 'Starting' to 'Started'.
Jun 14!14:54:41.124 debug QtDebugMsg: torcontrol: Control connection status changed from 'Unset' to 'Connecting' Jun 14!14:54:41.126 debug QtDebugMsg: torcontrol: Connecting to Tor (Attempt 1 of 5) Jun 14!14:54:41.126 debug QtDebugMsg: torcontrol: Starting control connection event loop. Jun 14!14:54:41.127 debug QtDebugMsg: torcontrol: Control connection status changed from 'Connecting' to 'Connected' Jun 14!14:54:41.143 notice Tor status changed from 'Started' to 'Authenticating'. Jun 14!14:54:41.147 debug QtDebugMsg: torcontrol: Control Command: PROTOCOLINFO 1 Jun 14!14:54:43.091 debug QtDebugMsg: torcontrol: Control Reply: 250 PROTOCOLINFO 1 250 AUTH METHODS=HASHEDPASSWORD 250 VERSION Tor='0.2.3.25' 250 OK Jun 14!14:54:43.092 notice Authenticating using 'hashed password' authentication. Replying to: Replying to: mttp - do you have any information about whether this applies to a specific architecture, or does it happen with both i386 and x8664?
Crap, I may have reported this incorrectly. It happened to one person who was using Windows 7 and one person who was using Linux; neither of them mentioned using the 64 bit packages. Mac OS users are experiencing an issue of a different nature, which I will open a separate ticket for. Never mind, I confirmed it is happening on Mac 32-bit package as well.