Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 28
    • Merge requests 28
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #7097
Closed
Open
Issue created Apr 16, 2014 by anonym@anonymMaintainer

Tor browser always displays the upgrade notification with Torbutton >= 1.6.8.0

Originally created by @anonym on #7097 (Redmine)

In our Tor browser builds, the pref torbrowser.version is set to Tails, and this does not work well together with upstream’s commit b9fb03cd (in Torbutton’s Git repo).

My guess is that there’s an assumption that torbrowser.version must look like an actual TBB version, like 3.5.4-Linux or whatever. With it set to something like Tails the upgrade notification is always blinking, suggesting that there’s an upgrade available.

Is this an upstream bug, or do we have to set torbrowser.version to something else from now on?

Feature Branch: feature/torbutton-1.6.9.0

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking