Bug 1881908 - Version checking error since Tor Browser 10.0 was released
Summary: Version checking error since Tor Browser 10.0 was released
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: torbrowser-launcher
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-23 11:08 UTC by Daniel Rusek
Modified: 2020-10-01 02:39 UTC (History)
3 users (show)

Fixed In Version: torbrowser-launcher-0.3.2-17.fc32 torbrowser-launcher-0.3.2-17.fc33 torbrowser-launcher-0.3.2-17.fc31
Clone Of:
Environment:
Last Closed: 2020-09-25 17:35:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Rusek 2020-09-23 11:08:46 UTC
Description of problem:
torbrowser-launcher does not work anymore since yesterday Tor Browser 10.0 release. There is already a simple fix available as a PR in the upstream GitHub repository, see Additional info.

Version-Release number of selected component (if applicable):
torbrowser-launcher-0.3.2-16.fc32.noarch

How reproducible:
Every time.

Steps to Reproduce:
1. Use clean Fedora system where torbrowser-launcher was previously not installed or make sure that Tor Browser was updated to 10.0.
2. Launch torbrowser-launcher.
3. Wait for the Tor Browser tarball to finish downloading.

Actual results:
"The version of Tor Browser you have installed is earlier than it should be, which could be a sign of an attack!" error is displayed.

Expected results:
Tor Browser is correctly downloaded and installed.

Additional info:
https://github.com/micahflee/torbrowser-launcher/pull/499

Comment 1 Fedora Update System 2020-09-23 13:57:12 UTC
FEDORA-2020-fe46bcff99 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe46bcff99

Comment 2 Fedora Update System 2020-09-23 15:28:03 UTC
FEDORA-2020-dca7111c17 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dca7111c17`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dca7111c17

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2020-09-23 17:22:26 UTC
FEDORA-2020-fe46bcff99 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fe46bcff99`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe46bcff99

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-09-23 17:41:36 UTC
FEDORA-2020-8763962ee1 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8763962ee1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8763962ee1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-09-25 17:35:53 UTC
FEDORA-2020-fe46bcff99 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2020-09-27 00:16:51 UTC
FEDORA-2020-dca7111c17 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-10-01 02:39:57 UTC
FEDORA-2020-8763962ee1 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.