touch-packages team mailing list archive

[zeus <1073669@xxxxxxxxxxxxxxxxxx>]

This bug is rather old, yet not solved. For the moment I'm using the script in this thread.
I'm on Ubuntu 14.04 (the issue persists also in Mint 14.04), Atheros bluetooth hardware (Toshiba Portégé Z830).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669

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

Status in rfkill package in Ubuntu:
  Confirmed

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
  following:

  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:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+subscriptions