My laptop runs ubuntu 16.04. Linux: 4.4.0-93-generic
I tried to debug this issue by compiling bluetoothd from source code.
Surprisingly, this issue is fixed after executing newly compiled bluetoothd 
instead of /usr/lib/bluetooth/bluetoothd.
Steps to build and run newly compiled bluetoothd is listed below.

sudo systemctl disable bluetooth.service 
sudo systemctl stop bluetooth.service 
* make sure bluetoothd started by systemd is stopped.
sudo systemctl status bluetooth.service 

* build bluetoothd
mkdir test
cd test/
apt-get source bluez
cd bluez-5.37/
sudo apt-get install libglib2.0-dev
sudo apt-get install libdbus-1-dev
sudo apt-get install libudev-dev
sudo apt-get install libical-dev
sudo apt-get install lib64readline-dev
sudo apt-get install libreadline-dev
./configure 
make
cd src/
ls
sudo ./bluetoothd -n
bluetooth may work now.

The drawback is that you have to start bluetoothd manually after reboot.
Good luck.

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

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to