This bug was fixed in the package torbrowser-launcher - 0.3.2-9ubuntu1
---------------
torbrowser-launcher (0.3.2-9ubuntu1) focal; urgency=medium
* This is a bug-fix only upload to address several significant bugs
found in the Tor Browser launcher package.
* Patches backported from Debian Unstable release and Debian Salsa git
repository for the package into the Focal package to fix issues.
The following patches were added in d/patches and added to the quilt
series file in the stated order:
- 0023-Update-Tor-Browser-Developers-public-key-481.patch: Fixes issue
with signature verification of tor browser tarball, due to changed
upstream developers key. (LP: #1856895)
- 0030-Use-gpg-instead-of-gpg2.patch: Use /usr/bin/gpg instead of the
/usr/bin/gpg2 symlink due to gnupg2 transitional package not being
part of default installations. (LP: #1897306)
- 0031-Use-better-version-string-comparison.patch: Properly handle the
version string comparison between Tor Browser versions, so that the
launcher supports version 10+ and can properly validate.
(LP: #1896752)
- 0032-apparmor-allow-Browser-to-memory-map-libstdc.patch: Allow
apparmor profile to access and memory map libstdc, due to AppArmor
default DENY on access causing issues. (LP: #1897302)
-- Thomas Ward <[email protected]> Sun, 27 Sep 2020 14:34:53 -0400
** Changed in: torbrowser-launcher (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897302
Title:
[SRU] Apparmor profile prevents Tor Browser from loading
libstdc++.so.6 since Tor Browser 10.0 was released
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1897302/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
