Hi Luiz!
Thanks for your advice. Now I am in a public library with a lot of
bluetooth devices around so I think the btmon has quite an unreadable
output. I will try to do it at home this evening. Instead I am postin
here the output for the deamon logs:
:~$ sudo journalctl --unit=bluetooth.service
-- Logs begin at mer 2019-05-29 14:39:16 CEST, end at mer 2019-05-29
14:53:13 CEST. --
mag 29 14:39:17 Sigmund-Lenovo systemd[1]: Starting Bluetooth service...
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Bluetooth daemon 5.37
mag 29 14:39:17 Sigmund-Lenovo systemd[1]: Started Bluetooth service.
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Starting SDP server
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Bluetooth management
interface 1.10 initialized
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Failed to obtain
handles for "Service Changed" characteristic
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Error adding Link Loss
service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Current Time Service
could not be registered
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: gatt-time-server:
Input/output error (5)
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Not enough free handles
to register service
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: Sap driver
initialization failed.
mag 29 14:39:17 Sigmund-Lenovo bluetoothd[1144]: sap-server: Operation
not permitted (1)
mag 29 14:39:23 Sigmund-Lenovo bluetoothd[1144]: Endpoint registered:
sender=:1.43 path=/MediaEndpoint/A2DPSource
mag 29 14:39:23 Sigmund-Lenovo bluetoothd[1144]: Endpoint registered:
sender=:1.43 path=/MediaEndpoint/A2DPSink
mag 29 14:39:54 Sigmund-Lenovo bluetoothd[1144]: Endpoint registered:
sender=:1.78 path=/MediaEndpoint/A2DPSource
mag 29 14:39:54 Sigmund-Lenovo bluetoothd[1144]: Endpoint registered:
sender=:1.78 path=/MediaEndpoint/A2DPSink
mag 29 14:39:54 Sigmund-Lenovo bluetoothd[1144]: RFCOMM server failed
for Headset Voice gateway: rfcomm_bind: Address already in use (98)
mag 29 14:40:11 Sigmund-Lenovo bluetoothd[1144]: Endpoint unregistered:
sender=:1.43 path=/MediaEndpoint/A2DPSource
mag 29 14:40:11 Sigmund-Lenovo bluetoothd[1144]: Endpoint unregistered:
sender=:1.43 path=/MediaEndpoint/A2DPSink
It seems that there are a lot of things that does not work... In any
case do you think that bluez 5.37 is the last version of bluez
compatible with my ubuntu 16.04 or there is some kind of broken package
in my system?
Thanks a lot!
Regards,
Matteo
Il 29/05/19 14:22, Luiz Augusto von Dentz ha scritto:
Hi Matteo,
On Tue, May 28, 2019 at 11:10 PM Matteo Formigli
<matteo.formigli@xxxxxxxxx> wrote:
Hi Luiz!
First, thanks for your answer! For now I can't upgrade my ubuntu, but I
already tried to upgrade bluez launching classic shell commands such as
apt-get update, upgrade and dist-upgrade. But bluez remains at version
5.37. I have to tell you that I tried to uninstall bluez and than
reinstall it. It was a gamble and maybe it went wrong, but I'm not sure.
About the logs and the HCI traces I don't have knowledge to provide you
what you want on my own. Can you tell me what commands i have to put in
the terminal?
5.37 is quite old so there is a high risk there something new, like
LE/GATT connection, that happens to be unstable at that point. You can
use btmon to collect the the HCI traces:
sudo btmon -t
You can also check the daemon logs with:
sudo journalctl --unit=bluetooth.service
Thanks in advance for your help!
Matteo
Il 28/05/19 20:54, Luiz Augusto von Dentz ha scritto:
Hi Matteo,
On Tue, May 28, 2019 at 9:38 PM Matteo Formigli
<matteo.formigli@xxxxxxxxx> wrote:
Hi all!
I am using Ubuntu 16.04 and there is no way to make the bluetooth work.
Every time I try to pair to my bluetooth headset bluez crashes. I really
don't know where to start solving this problem and I really hope that
someone on this list can help me.
Maybe it would help if you update your version of BlueZ, or better yet
update your ubuntu, if that still doesn't work then we may have a look
at some logs and HCI traces.
Thanks in advance for your help!
Matteo
P.s. The following is the output of the dpkg --status of the bluez packgage
:~$ dpkg --status bluez
Package: bluez
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 4119
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@xxxxxxxxxxxxxxxx>
Architecture: amd64
Multi-Arch: foreign
Version: 5.37-0ubuntu5.1
Replaces: bluez-alsa, bluez-audio (<= 3.36-3), bluez-input,
bluez-network, bluez-serial, bluez-utils (<= 3.36-3), udev (<< 170-1)
Depends: libc6 (>= 2.15), libdbus-1-3 (>= 1.9.14), libglib2.0-0 (>=
2.31.8), libreadline6 (>= 6.0), libudev1 (>= 196), init-system-helpers
(>= 1.18~), lsb-base (>= 4.1+Debian11ubuntu7), kmod, udev (>= 170-1), dbus
Breaks: udev (<< 170-1)
Conflicts: bluez-alsa, bluez-audio (<= 3.36-3), bluez-utils (<= 3.36-3)
Conffiles:
/etc/bluetooth/input.conf
/etc/bluetooth/main.conf
/etc/bluetooth/network.conf
/etc/bluetooth/proximity.conf
/etc/dbus-1/system.d/bluetooth.conf
/etc/init.d/bluetooth
/etc/init/bluetooth.conf
Description: Bluetooth tools and daemons
This package contains tools and system daemons for using Bluetooth
devices.
.
BlueZ is the official Linux Bluetooth protocol stack. It is an Open
Source
project distributed under GNU General Public License (GPL).
Homepage: http://www.bluez.org
Original-Maintainer: Debian Bluetooth Maintainers
<pkg-bluetooth-maintainers@xxxxxxxxxxxxxxxx
