Bug #14957

Document how to re-enable Bluetooth in the GNOME session

Added by intrigeri 2017-11-11 13:07:19 . Updated 2019-08-31 14:11:16 .

Status:
Confirmed
Priority:
Low
Assignee:
Category:
Hardware support
Target version:
Start date:
2017-11-11
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This is step 2 from https://mailman.boum.org/pipermail/tails-ux/2017-September/003454.html i.e.: document how to re-enable Bluetooth in the GNOME session and with Additional Software Packages (see commits 4fa1c46, 613b14c, 3d53d2c and 9320ca7 for inspiration).

Devices that are needed to log in via the Greeter (keyboard, mouse) are out of scope, which decreases the priority/usefulness of this ticket quite a bit, but still, at least one user has been asking for it since we did Bug #14655.

When we work on this, if the new set of commands needed to re-enable Bluetooth is substantially harder to remember and type by hand than the old one (rfkill + apt install), IMO we should provide a wrapper script.

Subtasks

Related issues

Related to Tails - Feature #10801: Make bluetooth opt-in in the Greeter Confirmed 2015-12-29
Related to Tails - Bug #14655: Ensure Tails is not affected by BlueBorne Resolved 2017-09-14

History

#1 Updated by intrigeri 2017-11-11 13:07:26

  • related to Feature #10801: Make bluetooth opt-in in the Greeter added

#2 Updated by intrigeri 2017-11-11 13:07:31

  • related to Bug #14655: Ensure Tails is not affected by BlueBorne added

#3 Updated by intrigeri 2017-11-11 13:08:25

  • Assignee set to intrigeri

For now this is a Research ticket as it’s not clear yet what exact set of commands need to be run, see the “[Tails-testers] Missing bluetooth” thread.

#4 Updated by intrigeri 2017-11-11 13:09:20

  • Description updated

#5 Updated by intrigeri 2018-03-27 11:43:28

We were reported that sudo rm /etc/modprobe.d/no-bluetooth.conf && sudo systemctl restart systemd-udev-trigger.service makes a Bluetooth mouse work but it causes all network interfaces to restart, WiFi stops working, and MAC spoofing is broken.

Also, reportedly this does nothing:

sudo rm /etc/modprobe.d/no-bluetooth.conf
sudo udevadm trigger --type=devices --subsystem-match=bluetooth --action=add
sudo rfkill unblock bluetooth
sudo apt install gnome-bluetooth

… and rfkill list still does not list bluetooth.

#6 Updated by intrigeri 2019-08-31 14:11:16

  • Assignee deleted (intrigeri)