New Tor Browser Bundles
The Tor Browser Bundles have been updated with a bunch of new software: Tor 0.2.2.37, Vidalia 0.2.19, and we have switched to using Firefox's long-term stable release (10.0.5esr).
Tor Browser Bundle (2.2.37-1)
- Update Tor to 0.2.2.37
- Switch Firefox to 10.0.5esr, since we will be tracking the extended stable releases for TBB stable versions
- Update Vidalia to 0.2.19
- Update Torbutton to 1.4.6
- Update NoScript to 2.4.4
I found using google this to be a known problem Tickets 5465 5261. I should have found these within torproject.org. How?
Basically the problem normally is harmless, if it doesnt stop the browser, that is. But it indicates Vidalia is trying to make a connections that it shouldnt.
The new L
I have mostly used Knoppix 6.2 (based on Debian) and never seen this problem. Perhaps that is what I should be worried about. Under Knoppix Vidalia succeeds making its unwanted connections. And does what?
Ticket 5261 is the most recent piece of information when I search the "Qt: Session management error" in Wiki Milestones and Tickets and rrandom says:
"It would be very bad if any part of TBB actually succeeded in talking to an X session manager. Can TBB-Vidalia ever connect to a session manager? Can TBB-Firefox ever connect to a session manager?"
The answer to these questions is found in Ticket 5465. Mainly:
It appears that Vidalia/Qt attempts to connect to a session manager iff the SESSION_MANAGER environment variable is set. RelativeLink.sh should unset that variable.
(Hopefully unsetting that variable will also keep Firefox from trying to talk to a session manager.)
It appears that Vidalia/Qt will be unable to connect to the session manager even if it attempts to, because the user's $HOME/.ICEauthority file is not present in the TBB directory. The GNOME 2 session manager did not log a message in $HOME/.xsession-errors when Vidalia failed to connect to it; hopefully other session managers won't log authentication errors either, but we shouldn't count on that.