In Ubuntu 16.04 LTS the error still persists. Should be fixed asap since
it affects any notebook I am running on 16.04 LTS.
--
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
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
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 reports "Not enough handles to register
On Ubuntu 16.10 with this bluez package:
Package: bluez
Version: 5.41-0ubuntu3with
I no longer see the "Not enough handles to register service" messages.
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to note that I had similar problems that were solved by cyano's suggestion
in #32
(Using Ubuntu 16.04 LTS with a cheap CSR8510 chip USB bluetooth dongle and
Clarity bluetooth speaker.)
sudo btmgmt le off
Then using the standard Bluetooth Settings app deleted the current
connection from
I was receiving many of the same errors in my logs, and after about 15+
fixes I tried, this was what ended up working. My main issue wasn't
really connecting the headset, it was keeping it connected for more than
a couple seconds and being able to play a2dp. Hopefully this works for
some of you.
I just tried running the command to turn off le when connected to a
device and I got the same message 'status 0x0a (Busy)' so perhaps you
are already connected to something.
My suggestion is to unpair all devices (if you have any paired) and running the
command:
rfkill block bluetooth
That
Just to -perhaps- add to any confusion: when I submit the command "sudo btmgmt
le off" in terminal, I expected the command to simply do its thing (switch off
le) and then return cli to the "waiting for input" status. Well, it doesn't:
when I submit the command and enter my password and press
Thanks for your suggestion; happy to try any solution suggestions.
When entering the command I get:
Set Low Energy for hci0 failed with status 0x0a (Busy)
Tried finding more information about this message but couldn't find anything
which seemed relevant.
Any suggestions?
(BTW: just to be
@aromo Similar issue, couldn't connect UE Boom speaker was just getting
'Unable to register GATT service with handle 0x0001'. Found it strange
that even when the speaker was powered down bluetoothd kept trying to
connect (and disconnect seconds later)
What I found was, UE Boom speakers can be
Hi all,
This bug affects me: Can't connect to my UE BOOM bluetooth speakers,
when I mess around with configuration and make it connect, the speaker
doesn't show up on the list of available speakers (Settings > Sound),
therefore, can't make them work.
16.04.1 LTS, kernel 4.4.0-59-generic.
#4 and
See question https://answers.launchpad.net/ubuntu-gnome/+question/424983
also.
I also see the message "Not enough free handles to register service".
Lenovo Ideapad 110.
Linux LPTP001 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Dec 31 16:02:49
On Lenovo w520, Ubuntu 16.04, kernel 4.4.0-57-generic, bluez 5.37-0ubuntu5,
unity desktop.
Same error messages relating to "Not enough free handles to register service".
Resuming from suspend results in bluetooth icon in title bar grayed out,
bluetooth switch is OFF, and bt mouse non-functional.
Same issue here, bluetooth mouse often hans.
journalctl --unit=bluetooth
-- Logs begin at 日 2016-12-11 10:01:22 CST, end at 日 2016-12-11 11:32:43 CST. --
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Bluetooth daemon 5.37
12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Starting SDP server
12月
Also experiencing this problem, on a pristine install of ubuntu 16.04.1 LTS
(4.4.0-45-generic #66-Ubuntu SMP, BlueZ version 5.37) onto a NUC6i5SYH.
I am doing nothing on the box, just setting it up.
The only packages I've installed are for sshd and bluez.
First run of the bluetooth service
I've enabled extended and debug logging (-E -d) in file:
/lib/systemd/system/bluetooth.service
was: ExecStart=/usr/lib/bluetooth/bluetoothd
now: ExecStart=/usr/lib/bluetooth/bluetoothd -E -d
Please find logs below, in attachments. Hope it will help to pin down
the problem.
$ uname -a
Linux xxx
I got this after accidentally starting the bluetooth service while playing
audio via a2dp.
The hackaround from #4 worked for me.
--
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
Related bugs: https://goo.gl/jh8wuP
--
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 reports "Not enough handles to register
service" at start
To manage
This affects me too:
$ journalctl | grep -i bluetooth
Jul 16 16:58:40 machine kernel: Bluetooth: Core ver 2.21
Jul 16 16:58:40 machine kernel: Bluetooth: HCI device and connection manager
initialized
Jul 16 16:58:40 machine kernel: Bluetooth: HCI socket layer initialized
Jul 16 16:58:40 machine
I messed around with this for ages with no luck on my Dell XPS 13 9350.
It seemed to even screw up the bluetooth when I rebooted back into
windows where I wasn't able to remove and re-pair my Microsoft Sculpt
Comfort Mouse.
Then through freak chance I plugged in an older microsoft usb mouse
(with
** Summary changed:
- 15:10: bluetoothd reports "Not enough handles to register service" at start
+ 15:10 and 16.04: bluetoothd reports "Not enough handles to register service"
at start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
20 matches
Mail list logo
