← Back to team overview

desktop-packages team mailing list archive

[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job


Happens with 16.04.
Goal: start ubuntu without bluetooth

+InitiallyPowered = false
Didn't work.

rfkill-restore.conf from this ticket
Didn't work.

+rfkill block bluetooth
Didn't work.

Finally disabled bluetooth from BIOS.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rfkill in Ubuntu.

  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to: