| 2019-12-18 21:01:49 |
Jeffrey Walton |
bug |
|
|
added bug |
| 2019-12-18 21:04:11 |
Jeffrey Walton |
summary |
Tor does not download and install; repeated verifcation failed |
Tor does not download and install; repeated signature verification failed |
|
| 2019-12-19 14:49:25 |
Jeffrey Walton |
tags |
|
apport-collected bionic |
|
| 2019-12-19 14:49:26 |
Jeffrey Walton |
description |
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic] |
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True |
|
| 2019-12-19 14:49:27 |
Jeffrey Walton |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1856895/+attachment/5314040/+files/Dependencies.txt |
|
| 2019-12-19 14:49:28 |
Jeffrey Walton |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1856895/+attachment/5314041/+files/ProcCpuinfoMinimal.txt |
|
| 2019-12-19 14:55:00 |
Jeffrey Walton |
description |
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True |
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
|
| 2019-12-19 14:55:01 |
Jeffrey Walton |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1856895/+attachment/5314046/+files/Dependencies.txt |
|
| 2019-12-19 14:55:02 |
Jeffrey Walton |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1856895/+attachment/5314047/+files/ProcCpuinfoMinimal.txt |
|
| 2019-12-19 15:07:08 |
Peter Palfrader |
affects |
tor (Ubuntu) |
torbrowser-launcher (Ubuntu) |
|
| 2020-09-07 12:16:17 |
AsciiWolf |
bug watch added |
|
https://github.com/micahflee/torbrowser-launcher/issues/485 |
|
| 2020-09-07 12:16:37 |
AsciiWolf |
tags |
apport-collected bionic |
apport-collected bionic focal |
|
| 2020-09-07 12:18:53 |
Launchpad Janitor |
torbrowser-launcher (Ubuntu): status |
New |
Confirmed |
|
| 2020-09-09 09:34:23 |
AsciiWolf |
bug |
|
|
added subscriber #ubuntu-motu IRC Operators |
| 2020-09-09 09:41:39 |
rww |
removed subscriber #ubuntu-motu IRC Operators |
|
|
|
| 2020-09-18 10:30:48 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2020-09-18 10:31:12 |
Robie Basak |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2020-09-25 16:22:22 |
Thomas Ward |
nominated for series |
|
Ubuntu Focal |
|
| 2020-09-25 16:22:22 |
Thomas Ward |
bug task added |
|
torbrowser-launcher (Ubuntu Focal) |
|
| 2020-09-25 16:22:27 |
Thomas Ward |
torbrowser-launcher (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2020-09-25 16:22:29 |
Thomas Ward |
torbrowser-launcher (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-09-25 16:22:31 |
Thomas Ward |
torbrowser-launcher (Ubuntu Focal): assignee |
|
Thomas Ward (teward) |
|
| 2020-09-28 13:40:32 |
Thomas Ward |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-09-28 13:40:32 |
Thomas Ward |
bug task added |
|
torbrowser-launcher (Ubuntu Bionic) |
|
| 2020-09-28 13:58:47 |
Thomas Ward |
description |
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
[Impact]
torbrowser-launcher does not have the ability to update to newer Tor. New downloads of updates through it fail to verify due to mismatched developer keys.
[Test Case]
(1) Install torbrowser-launcher.
(2) Attempt to start tor.
(3) Tor will attempt to update and fail with a signature verification error.
[Regression Potential]
Replacing the key to use for verification should have no impact on functionality, but older-signed versions of the tor browser tarball will fail to verify. However, Tor devs are saying to use the new key anyways, so we should replace the key anyways.
------
------
[Original Bug Description]
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
|
| 2020-09-28 13:58:52 |
Thomas Ward |
summary |
Tor does not download and install; repeated signature verification failed |
[SRU] Tor does not download and install; repeated signature verification failed |
|
| 2020-09-29 16:52:20 |
Robie Basak |
description |
[Impact]
torbrowser-launcher does not have the ability to update to newer Tor. New downloads of updates through it fail to verify due to mismatched developer keys.
[Test Case]
(1) Install torbrowser-launcher.
(2) Attempt to start tor.
(3) Tor will attempt to update and fail with a signature verification error.
[Regression Potential]
Replacing the key to use for verification should have no impact on functionality, but older-signed versions of the tor browser tarball will fail to verify. However, Tor devs are saying to use the new key anyways, so we should replace the key anyways.
------
------
[Original Bug Description]
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
[Impact]
torbrowser-launcher does not have the ability to update to newer Tor. New downloads of updates through it fail to verify due to mismatched developer keys.
[Test Case]
(1) Install torbrowser-launcher.
(2) Attempt to start tor.
(3) Tor will attempt to update and fail with a signature verification error.
[Regression Potential]
Replacing the key to use for verification should have no impact on functionality, but older-signed versions of the tor browser tarball will fail to verify. However, Tor devs are saying to use the new key anyways, so we should replace the key anyways.
[racb] We might have overlooked some case where the old key is still required.
------
------
[Original Bug Description]
I'm working on Ubuntu 18.04 x86_64 (fully patched). I installed Tor using Apt. When I attempt to launch Tor I am in an endless loop of download/verify/verify-failed.
The process at the moment is (1) Try to start Tor. (2) Tor downloads something. (3) Signature verification begins. (4) Signature verification fails. (5) Click "Start" to do it again.
Clicking "Start" from the "signature verify failed" screen takes me back to the download. Ad infinitum.
I have to go to a Windows machine to use Tor. I'd like to get the issue fixed on Ubuntu since it is my main workstation. This issue has been going on since about June 2018. I'm guessing someone does not realize something is broken.
At this point I am willing to accept the bad signature so I can use the Tor browser. I'm ready for the 6 month DoS to end.
Screenshots available at https://superuser.com/q/1511112/173513.
-----
Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
And Tor package:
$ apt list --installed | grep -w -i tor
tor/bionic,now 0.3.2.10-1 amd64 [installed,automatic]
tor-geoipdb/bionic,bionic,now 0.3.2.10-1 all [installed,automatic]
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-20 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: tor 0.3.2.10-1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Tags: bionic
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
|
| 2020-09-30 19:04:11 |
Robie Basak |
torbrowser-launcher (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-09-30 19:04:13 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-09-30 19:04:15 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2020-09-30 19:04:19 |
Robie Basak |
tags |
apport-collected bionic focal |
apport-collected bionic focal verification-needed verification-needed-focal |
|
| 2020-09-30 20:25:58 |
AsciiWolf |
tags |
apport-collected bionic focal verification-needed verification-needed-focal |
apport-collected bionic focal verification-done-focal verification-needed |
|
| 2020-10-06 13:35:28 |
Thomas Ward |
tags |
apport-collected bionic focal verification-done-focal verification-needed |
apport-collected bionic focal verification-done-focal |
|
| 2020-10-12 08:46:59 |
Launchpad Janitor |
torbrowser-launcher (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-10-12 08:47:11 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-10-12 13:50:17 |
Thomas Ward |
torbrowser-launcher (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-10-12 13:50:20 |
Thomas Ward |
torbrowser-launcher (Ubuntu Bionic): assignee |
|
Thomas Ward (teward) |
|
| 2020-10-13 17:32:38 |
Brian Murray |
torbrowser-launcher (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-10-13 17:32:40 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-10-13 17:32:46 |
Brian Murray |
tags |
apport-collected bionic focal verification-done-focal |
apport-collected bionic focal verification-done-focal verification-needed verification-needed-bionic |
|
| 2020-10-14 22:29:42 |
Thomas Ward |
tags |
apport-collected bionic focal verification-done-focal verification-needed verification-needed-bionic |
apport-collected bionic focal verification-done-bionic verification-done-focal |
|
| 2020-10-19 15:11:50 |
Launchpad Janitor |
torbrowser-launcher (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
