Package: bluez Version: 5.33-1 Severity: normal On 2015-08-27 the bluez package on my system was upgraded. After that upgrade, my machine stopped being able to connect to devices which had been working fine before the upgrade.
Actually, it appears that the devices "connect", in the sense that my device beams and appears to indicate that it was a host, but the device is not available to use on my system. Journalctl logs after restarting the bluetooth service: Aug 29 14:06:13 servo systemd[1]: Started Bluetooth service. Aug 29 14:06:13 servo bluetoothd[3197]: Starting SDP server Aug 29 14:06:13 servo bluetoothd[3197]: Bluetooth management interface 1.9 initialized Aug 29 14:06:13 servo bluetoothd[3197]: Failed to obtain handles for "Service Changed" characteristic Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Error adding Link Loss service Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Current Time Service could not be registered Aug 29 14:06:13 servo bluetoothd[3197]: gatt-time-server: Input/output error (5) Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Not enough free handles to register service Aug 29 14:06:13 servo bluetoothd[3197]: Sap driver initialization failed. Aug 29 14:06:13 servo bluetoothd[3197]: sap-server: Operation not permitted (1) Aug 29 14:06:13 servo bluetoothd[3197]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource Aug 29 14:06:13 servo bluetoothd[3197]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink Everything from "Failed to obtain..." to ""sap-server:..." is red. Every attempt to restart the service produces the same errors. bluetoothctl also don't work anymore, keeps producing these "org.bluez.Error.NotReady" errors: servo:~ 0$ bluetoothctl [NEW] Controller F8:2F:A8:EB:6A:04 servo-0 [default] [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# info 00:0C:8A:E1:1C:56 Device 00:0C:8A:E1:1C:56 not available [bluetooth]# connect 00:0C:8A:E1:1C:56 Device 00:0C:8A:E1:1C:56 not available [bluetooth]# jamie. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluez depends on: ii dbus 1.9.8-1 ii init-system-helpers 1.23 ii kmod 21-1 ii libc6 2.19-19 ii libdbus-1-3 1.9.8-1 ii libglib2.0-0 2.44.1-1.1 ii libreadline6 6.3-8+b3 ii libudev1 224-1 ii lsb-base 4.1+Debian14 ii udev 224-1 bluez recommends no packages. bluez suggests no packages. -- no debconf information
