Originally published at: News - Whonix Forum
If you do not use any accessibility tools (gnome-orca, espeakup, console-braille, florence, dasher, kdeaccessibility, kvkbd, kmousetool, kmag, kmouth, jovie, xbrlapi, festival, qt-at-sp), you will not miss anything. (You would probably know if you are using them.)
Soon, there will be a Whonix stable upgrade. The package whonix-gateway-shared-packages-shared-meta will no longer depend on anon-shared-kde-accessibility. This means, when you run sudo apt-get purge kdeaccessibility && sudo apt-get autoremove
after the upgrade, these accessibility packages will be automatically removed.
Non-Qubes-Whonix only: brltty should be removed, since it currently is causing a performance issue.
Otherwise if you just want to remove brltty, use sudo apt-get purge brltty
. If you want to keep almost all or only not those you manually uninstalled, you can use sudo aptitude keep-all
.
If you want these installed, you are still very much free to have them installed. Just install them the usual way.
This is because those have some issues.
- /var/log/syslog spam host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device
- That is a performance issue.
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845496
- https://forums.whonix.org/t/brltty-floods-both-syslog-and-daemon-log
- brltty is problematic, because it opens an local listener port, which would be insecure for the upcoming Whonix 14 Tor ControlPort add_onion support.
- espeakup systemd unit restart fails during jessie to stretch upgrades.
- Running `sudo apt-get dist-upgrade` therefore must be run multiple times, which is a usability issue.
sudo systemctl stop brltty
sudo systemctl mask brltty