This bug was fixed in the package torbrowser-launcher - 0.3.7-1ubuntu1
---
torbrowser-launcher (0.3.7-1ubuntu1) noble; urgency=medium
* Fix non-functional keyboard (LP: #2056578).
-- Thomas Ward Thu, 06 Jun 2024 19:15:35 -0500
** Changed in: torbrowser-launcher (Ubuntu Noble)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056578
Title:
[SRU - Noble] Tor Browser - keyboard not functioning
To manage
I did set up two (clean installation, fully updated) 24.04 VMs: one with
noble-proposed disabled and the other one with noble-proposed enabled.
Installed latest torbrowser-launcher on both of them.
- On the VM without noble-proposed enabled and using torbrowser-launcher
version 0.3.7-1build2,
Thanks for the upload as well.
Ideally, the version should be `0.3.7-1ubuntu0.1` (not `ubuntu1`), as this
is for stable release (see [1]), but in this case it's fine -- the version
hasn't been used (see [2]), and will not be used anymore, as devel release
is already at `0.3.7-2`.
Now, I'd
Thanks for mentioning that the proposed change is present in Firefox AppArmor
profiles.
Looking at its snap profiles, this can be traced back to snapd; that builds
confidence.
For documentation purposes:
$ sudo apt update && sudo apt install -y firefox
$ dpkg -s firefox | grep ^Description:
Marking Oracular as Fix Released.
torbrowser-launcher (0.3.7-2) unstable; urgency=medium
[ Daniel Rusek ]
* debian/patches:
- Add patch 05 to fix keyboard input issue.
...
** Changed in: torbrowser-launcher (Ubuntu Oracular)
Status: Invalid => Fix Released
--
You received this
Thank you very much gypearce, that worked just fine :)
I added the line right after:
# KDE 4
owner @{HOME}/.kde/share/config/* r,
Thank you again for made the fix accessible for the noobs! <3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
[Impact]
Due to various changes in AppArmor, and the AppArmor policy for Tor Browser
installed by the launcher, the default ibus/dbus abstractions don't include
user-space access to DBUS/IBUS.
This results in Tor Browser being unable to read keyboard input in
