This bug effects 128 people and closing it because you don't like the
title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug
report in the hopes it will be solved:

https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not-
enough-free-handles-to-register-service-error

and

https://askubuntu.com/questions/773629/16-04-bluetooth-error-not-enough-
free-handles-to-register-service

A Debian bug report suggests a solution by using -E (experimental)
parameter on the systemd service exec doesn't work for Ubuntu 16.04,
Kernel 4.14.4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949

When a hundred reported people are effected by "Not enough free handles
to register service" and you don't want to look at it because the bug
title isn't right, why not simply change the title?

Something else to consider are the thousands of people effected by
bluetooth connection problems, re-pairing, etc. What if the root of
their problems was this bug that you don't want to look at?

** Bug watch added: Debian Bug tracker #813949
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949

-- 
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 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

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