I use ubuntu16.04, my computer can't connect to my bluetooth speaker
after reboot.
uname -a
Linux zs-PC 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
journalctl --unit=bluetooth
-- Logs begin at 一 2016-06-20 18:41:21 CST, end at 一 2016-06-20 18:43:45
Sorry, I was wrong, the problem occurs in Gnome as well, but not every
time.
--
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: bluetoothd reports "Not enough handles
I switched to Gnome, where I do not have this problem. Apparently it has
something to do with Unity.
--
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: bluetoothd
I have this bug too, on 16.04. After booting bluetooth works fine, then
after suspend it's gone, and I get the 'not enough handles' errors. Only
rebooting works. The solution of amias does not work for me.
--
You received this bug notification because you are a member of Kernel
Packages, which
I have a possible variant of this bug in 16.10 with a 4.4.0-22 (standard
kernel at time of writing), after a day or so of uptime i start to get
these messages. they seem to go away after a log out and login.
This is on a dell precision m3800 using plantronic back beat pro
headphones , this
On 15/04/16 03:19, Laurent Bonnaud wrote:
>> All tests produced the "not enough handles" message from bluetoothd.
>> Is anyone successfully using bluetooth with these later ubuntu kernels?
>
> On both of my systems I get the "not enough handles" messages but I got BT to
> work for both my use
> All tests produced the "not enough handles" message from bluetoothd.
> Is anyone successfully using bluetooth with these later ubuntu kernels?
On both of my systems I get the "not enough handles" messages but I got BT to
work for both my use cases:
- using a BT mouse on a laptop
- streaming
I also true using an old bluetooth usb dongle. I used it on the asus
T300, but that made no difference. I also tried it on my dell 1558
laptop, with 16.04 (64-bit) and 15.10 (32-bit with bluez 5.35). The
16.04 test was basically the same as on the asus. The 15.10 test was
different in detail, but
Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was
This bug still exists in xenial with kernel 4.5:
$ uname -a
Linux xeelee 4.5.0-040500-lowlatency #201603140130 SMP PREEMPT Mon Mar 14
05:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ journalctl |grep bluetoothd
Apr 08 20:24:43 xeelee bluetoothd[929]: Bluetooth daemon 5.37
Apr 08 20:24:43
Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was
@Brian Burch - You might get more run time if you minimize the bt device
manager window instead of closing it after pairing (assuming that you
are using blueman device manager.) I find kernel 4.5 works a little bit
better with bluetooth. kernel 4.3.6 works like I'd expect with
bluetooth, if you
Same messages for me with 16.04 beta2, running with bluez 5.37-0ubuntu5
on 4.4.0-15-generic amd64 kernel. Running on Asus T300 CHI notepad with
bluetooth keyboard/touchpad docking unit. It pairs OK, but connection
comes up briefly and then drops again.
bluetoothctl log extract follows:
[CHG]
2 updates: 4.5.0-next-20160321: bluetooth self-starts like 4.3.6 used
to. I still need to open device manager to maintain connections, but I
no longer have to manually search for already paired devices.
The "failed to obtain..." messages are in journalctl not dmesg. Sorry
for any confusion
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
do we have any follow up on this bug? needs more info?
--
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: bluetoothd reports "Not enough handles to register service"
Thank you for mentioning that you can manually add the device. My mouse
wasn't paired even using the hardware buttons. Going to the bluetooth
manager and selecting the mouse did work. I've added the udev rules in
the hope I won't need to do this manually each time. Thank you.
--
You received
#3 seems to be correct.
I added the following lines to the end of /etc/pulse/system.pa:
### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module
This pretty much looks like the adapter is just not automatically
enabled again after you restart the service. There is currently a udev
workaround rule in place to active a Bluetooth adapter directly at
login-screen time which wouldn't kick in here again. If there is no
general power state saver
This also occurs from a fresh boot:
Aug 30 23:42:21 hephaestion.lan.iam.tj systemd[1]: Starting Bluetooth service...
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Bluetooth daemon 5.33
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Starting SDP server
Aug 30 23:42:21
20 matches
Mail list logo