I have these errors in my dmesg with kernel 4.5.0 but not in 4.3.6 where
bluetooth works great.  Kernel 4.4.x bluetooth behaves the same as 4.5.0
but I hadn't noticed if there are  "failed to obtain..." messages.

When I boot in 4.3.6 bluetooth (bluez 5.35 and blueman, and a command
btattach... in /etc/rc.local) starts fine and I don't have to do much to
wake-up my bluetooth mouse and keyboard.  In 4.4+ I have to manually
search for the devices, but I don't have to pair them again.  I then
have to leave the blueman device manager running (minimized.)  If
anything times out from inactivity, I have to search again to reconnect.

Asus T100-CHI Ubuntu 15.10-i386.  Minimally patch kernel supports a lot
of the hardware of the T100, except sound, cameras, mic...  Bluetooth
started working in kernel 4.3.3+ but regressed starting with
4.4-rc1->4.5.0.

I see a reference to a udev workaround, but that is a new area to me.
The example seems aimed at audio - how would I adapt that to
mouse/keyboard?

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to