Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #5465

Closed
Open
Opened Mar 24, 2012 by Robert Ransom@rransom

Unset SESSION_MANAGER env var in TBB-Linux RelativeLink.sh

On startup, Vidalia often complains that it could not authenticate to the user's X session manager:

Qt: Session management error: None of the authentication protocols specified are supported

Vidalia should not be attempting to connect to a session manager, and the fact that it does could leave traces on disk outside the TBB directory.

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.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#5465