[Bug 781556] Re: bluetooth discovery fails: no devices found during scan

[Mathieu Trudel-Lapierre]

I'm still not convinced that this should be covered by a udev rule in
bluez; seems to me like this will conflict with the killswitch states
for the device, which appear to me as more important to preserve in all
cases. (For instance, booting your computer in a plane shouldn't cause
the udev rule to trigger and radio to be turned on despite the
killswitch state being off, and it's unclear yet how this reacts). The
patch looks technically correct and seems like it will do the right
thing, but it seems a little dangerous to assume the radio should just
be turned on (and that's the driver's job anyway)

May I suggest fixing this at the linux kernel driver level instead? I'll
open a linux task in case.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Medium

** Tags added: bot-stop-nagging

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/781556

Title:
  bluetooth discovery fails: no devices found during scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/781556/+subscriptions