Bluetooth is dead

pedrogabriel · 2015-07-27 04:07:00

I'm facing the same problem here. Did you send a bug report for it?

hoeffl · 2015-07-28 15:05:56

Sadly, I don't know what I did exactly, but my headset is now working (after having the above problem for quite some time)... A few things I did:

1. I deleted ~/.config/pulse.

2. I removed a call to

start-pulseaudio-x11

from my .xinitrc. I did this mainly because I had a feeling that perhaps multiple instances of pulseaudio were running (and interfering with each other?).

pgrep pulseaudio

always returned 4 to 5 PIDs, now there is only one PID returned again.

3. I added

load-module module-switch-on-connect

to /etc/pulse/default.pa (yet, I'm pretty sure this has nothing to do with this problem).

4. I unpaired and repaired my headset (this is actually the only bluetooth-specific thing I did, everything else was rather pulseaudio-specific -- which might lead to the conclusion that pulseaudio is the real problem?).

5. I restarted pulseaudio with

pulseaudio -k; pulseaudio --start

quite a few times (yet it did not always work).

I should probably also state, that I don't know a lot about pulseaudio (which might be obvious from some stupid things I did unknowingly ;-) ).

AnAkkk · 2015-07-28 17:50:38

I have exactly the same issue, bluetooth has been broken since a while.

juil. 28 18:12:00 laptop bluetoothd[602]: Failed to obtain handles for "Service Changed" characteristic
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Error adding Link Loss service
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Current Time Service could not be registered
juil. 28 18:12:00 laptop bluetoothd[602]: gatt-time-server: Input/output error (5)
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Not enough free handles to register service
juil. 28 18:12:00 laptop bluetoothd[602]: Sap driver initialization failed.
juil. 28 18:12:00 laptop bluetoothd[602]: sap-server: Operation not permitted (1)

EDIT: According to people #bluez-users IRC these errors are not related to audio, and I was able to send a bluetooth file to my phone while I have these errors, so I guess everything is fine for me now.

Last edited by AnAkkk (2015-07-28 18:54:15)

graysky · 2015-08-09 15:33:47

I have an MSI H97I board that has onboard bluetooth with the same errors upon starting the bluetooth service... but /usr/lib/bluetooth/bluetoothd is running...

% status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: disabled)
   Active: active (running) since Sun 2015-08-09 11:30:16 EDT; 3s ago
     Docs: man:bluetoothd(8)
 Main PID: 841 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─841 /usr/lib/bluetooth/bluetoothd

Aug 09 11:30:16 athens bluetoothd[841]: Error adding Link Loss service
Aug 09 11:30:16 athens bluetoothd[841]: Not enough free handles to register service
Aug 09 11:30:16 athens bluetoothd[841]: Not enough free handles to register service
Aug 09 11:30:16 athens bluetoothd[841]: Not enough free handles to register service
Aug 09 11:30:16 athens bluetoothd[841]: Current Time Service could not be registered
Aug 09 11:30:16 athens bluetoothd[841]: gatt-time-server: Input/output error (5)
Aug 09 11:30:16 athens bluetoothd[841]: Not enough free handles to register service
Aug 09 11:30:16 athens bluetoothd[841]: Not enough free handles to register service
Aug 09 11:30:16 athens bluetoothd[841]: Sap driver initialization failed.
Aug 09 11:30:16 athens bluetoothd[841]: sap-server: Operation not permitted (1)

% ps aux | grep blue
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       981  0.0  0.0  19692  3848 ?        Ss   11:35   0:00 /usr/lib/bluetooth/bluetoothd

I can also use bluetoothctl to pair devices (a keyboard in this case) but it is non-functional. Thoughts?

% sudo bluetoothctl
[NEW] Controller 80:86:F2:5F:79:35 athens [default]
[NEW] Device 7C:ED:2D:68:52:D7 Microsoft Bluetooth Mobile Keyboard 6000
[bluetooth]# paired-devices 
Device 7C:ED:2D:68:52:D7 Microsoft Bluetooth Mobile Keyboard 6000

Last edited by graysky (2015-08-09 16:03:31)

TheSaint · 2015-08-10 19:08:45

Filing a bug report ?

joshdmiller · 2015-09-08 16:21:48

hoeffl wrote:

1. I deleted ~/.config/pulse.

This solved the same series of errors for me. Yay! (not sure why, though)

A little more detail: I have been using the same Bluetooth headset with bluez and pulse for many months. I recently connected a bluetooth speaker (actually an Amazon Echo), and my headset refused to connect with the errors mentioned here. Then I removed the Echo, which solved nothing, and then the Echo refused to connect with the same errors. Deleting the pulse config solved the issue.

I have not yet tried to connect the Echo again to see if I can establish a causal relationship.

Malstrond · 2015-10-16 20:05:30

Same problem here with a mouse. Googling was also unsucessful because the first search result is the source of patch introducing the error message and the second result is this thread...

bluetoothctl exchange:

[bluetooth]# agent on
Agent registered
[bluetooth]# scan on
[NEW] Device D7:F4:D0:76:E1:F3 Arc Touch Mouse SE
[CHG] Device D7:F4:D0:76:E1:F3 Connected: yes
[CHG] Device D7:F4:D0:76:E1:F3 UUIDs: 1800
[CHG] Device D7:F4:D0:76:E1:F3 UUIDs: 1801
[CHG] Device D7:F4:D0:76:E1:F3 UUIDs: 180a
[CHG] Device D7:F4:D0:76:E1:F3 UUIDs: 180f
[CHG] Device D7:F4:D0:76:E1:F3 UUIDs: 1812
[bluetooth]# devices
Device 68:64:4B:16:F3:C8 68-64-4B-16-F3-C8
Device D7:F4:D0:76:E1:F3 Arc Touch Mouse SE
[bluetooth]# pair D7:F4:D0:76:E1:F3
Attempting to pair with D7:F4:D0:76:E1:F3
[CHG] Device D7:F4:D0:76:E1:F3 Paired: yes
Pairing successful
[bluetooth]# trust D7:F4:D0:76:E1:F3
[CHG] Device D7:F4:D0:76:E1:F3 Trusted: yes
Changing D7:F4:D0:76:E1:F3 trust succeeded
[bluetooth]# connect D7:F4:D0:76:E1:F3
Attempting to connect to D7:F4:D0:76:E1:F3
Connection successful
[CHG] Device 68:64:4B:16:F3:C8 RSSI: -84
[bluetooth]# info D7:F4:D0:76:E1:F3
Device D7:F4:D0:76:E1:F3
	Name: Arc Touch Mouse SE
	Alias: Arc Touch Mouse SE
	Appearance: 0x03c2
	Icon: input-mouse
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID:                           (1800)
	UUID:                           (1801)
	UUID:                           (180a)
	UUID:                           (180f)
	UUID:                           (1812)
	RSSI: -51

Everything appears to work, but no new input device is created.

hciconfig says that there is traffic on the interface:

# hciconfig hci0
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 64:76:BA:8C:82:91  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING 
	RX bytes:6275 acl:162 sco:0 events:275 errors:0
	TX bytes:6154 acl:12 sco:0 commands:215 errors:0

bluetoothd and kernel output:

Okt 16 21:41:23 tarsonis bluetoothd[1447]: Bluetooth daemon 5.35
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Starting SDP server
Okt 16 21:41:23 tarsonis dbus[489]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Bluetooth management interface 1.10 initialized
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Failed to obtain handles for "Service Changed" characteristic
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Error adding Link Loss service
Okt 16 21:41:23 tarsonis systemd[1]: Starting Hostname Service...
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Current Time Service could not be registered
Okt 16 21:41:23 tarsonis bluetoothd[1447]: gatt-time-server: Input/output error (5)
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Not enough free handles to register service
Okt 16 21:41:23 tarsonis bluetoothd[1447]: Sap driver initialization failed.
Okt 16 21:41:23 tarsonis bluetoothd[1447]: sap-server: Operation not permitted (1)
Okt 16 21:41:23 tarsonis dbus[489]: [system] Successfully activated service 'org.freedesktop.hostname1'
Okt 16 21:41:23 tarsonis systemd[1]: Started Hostname Service.
Okt 16 21:43:46 tarsonis kernel: Bluetooth: SMP security requested but not available
Okt 16 21:43:46 tarsonis bluetoothd[1447]: Unable to register GATT service with handle 0x0011 for device D7:F4:D0:76:E1:F3:
Okt 16 21:43:46 tarsonis bluetoothd[1447]: Error reading PNP_ID value: Attribute requires authentication before read/write
Okt 16 21:47:18 tarsonis kernel: usb 1-3.3: reset full-speed USB device number 10 using xhci_hcd
Okt 16 21:47:20 tarsonis kernel: Bluetooth: hci0 command 0x2005 tx timeout
Okt 16 21:47:22 tarsonis kernel: Bluetooth: hci0 command 0x200b tx timeout
Okt 16 21:47:24 tarsonis kernel: Bluetooth: hci0 command 0x200c tx timeout

The USB device mentioned is part of the controller:

# lsusb -s 001:003 -v

Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0         8
  idVendor           0x0a5c Broadcom Corp.
  idProduct          0x4500 BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
  bcdDevice            1.00
  iManufacturer           1 Apple Inc.
  iProduct                2 BRCM20702 Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower               94mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval             255
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             3
  wHubCharacteristic 0x0004
    Ganged power switching
    Compound device
    Ganged overcurrent protection
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent    100 milli Ampere
  DeviceRemovable    0x0e
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0100 power
   Port 2: 0000.0100 power
   Port 3: 0000.0103 power enable connect
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0001
  Self Powered

tomputzeys · 2015-10-19 18:59:17

In my case, resetting the hci device solved my problems:

# sudo hciconfig -a hci0 reset

Ekaradon · 2015-10-20 11:43:54

Since last update, I had always this type of message:

-- Logs begin at Mon 2015-09-14 19:10:34 CEST, end at Tue 2015-10-20 11:52:02 CEST. --
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13317 us (= 2348 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14209 us (= 2504 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13349 us (= 2352 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13191 us (= 2324 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13283 us (= 2340 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14380 us (= 2536 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13265 us (= 2336 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13195 us (= 2324 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13408 us (= 2364 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14253 us (= 2512 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13221 us (= 2332 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13332 us (= 2348 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13204 us (= 2328 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14355 us (= 2532 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13212 us (= 2328 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13303 us (= 2344 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13324 us (= 2348 bytes) in audio stream
Oct 20 11:52:01 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14304 us (= 2520 bytes) in audio stream
Oct 20 11:52:02 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13255 us (= 2336 bytes) in audio stream
Oct 20 11:52:02 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13287 us (= 2340 bytes) in audio stream

I don't know why because my hardware is still the same and I found no one facing this specific issue. However, bluetooth seems to be unstable as I read it here. So I tried the following solutions:

# sudo systemctl stop bluetooth.service
# rm -rf ~/.config/pulse
# sudo hciconfig -a hci0 reset
# sudo systemctl start bluetooth.service

EDIT: It stills do not work:

-- Logs begin at Mon 2015-09-14 19:10:34 CEST, end at Tue 2015-10-20 13:51:28 CEST. --
Oct 20 13:51:27 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14230 us (= 2508 bytes) in audio stream
Oct 20 13:51:27 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13289 us (= 2344 bytes) in audio stream
Oct 20 13:51:28 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13289 us (= 2344 bytes) in audio stream
Oct 20 13:51:28 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13239 us (= 2332 bytes) in audio stream
Oct 20 13:51:28 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 14283 us (= 2516 bytes) in audio stream
Oct 20 13:51:28 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13301 us (= 2344 bytes) in audio stream
Oct 20 13:51:28 host pulseaudio[7109]: W: [bluetooth] module-bluez5-device.c: Skipping 13340 us (= 2352 bytes) in audio stream

I have not found anything not too old relevant about this issue. Is anyone facing this issue or having a clue about this bug?

Last edited by Ekaradon (2015-10-20 11:54:08)

joejoejoe · 2015-10-31 21:21:07

I've got those same errors many have reported, and gnome-bluetooth shows no devices. However, blueman works, and shows devices. So I guess that's good enough for now.

TheSaint · 2015-12-04 07:14:47

I changed the dongle and it seems that it works. I hope that this dongle will last, as it's USB 3.0 compatible.

fabioamd87 · 2015-12-04 10:43:46

dongle name and model?

TheSaint · 2015-12-22 01:07:12

$ lsusb
8<-----
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

But I'm afraid it won't last too. Average they die after 3 weeks.
And now I discovered that isn't a USB3.0 dongle

deFreitas · 2023-03-02 05:38:11

Take a look at this, answer, it may help you https://unix.stackexchange.com/a/738371/117844

2ManyDogs · 2023-03-03 12:21:37

drFreitas, please do not necrobump.

Closing.

Arch Linux

#26 2015-07-27 04:07:00

Re: Bluetooth is dead

#27 2015-07-28 15:05:56

Re: Bluetooth is dead

#28 2015-07-28 17:50:38

Re: Bluetooth is dead

#29 2015-08-09 15:33:47

Re: Bluetooth is dead

#30 2015-08-10 19:08:45

Re: Bluetooth is dead

#31 2015-09-08 16:21:48

Re: Bluetooth is dead

#32 2015-10-16 20:05:30

Re: Bluetooth is dead

#33 2015-10-19 18:59:17

Re: Bluetooth is dead

#34 2015-10-20 11:43:54

Re: Bluetooth is dead

#35 2015-10-31 21:21:07

Re: Bluetooth is dead

#36 2015-12-04 07:14:47

Re: Bluetooth is dead

#37 2015-12-04 10:43:46

Re: Bluetooth is dead

#38 2015-12-22 01:07:12

Re: Bluetooth is dead

#39 2023-03-02 05:38:11

Re: Bluetooth is dead

#40 2023-03-03 12:21:37

Re: Bluetooth is dead

Board footer