Arch Linux

jyaworski

Member

Registered: 2011-06-20

Posts: 16

Bluetooth: update causes microphone to not function

It appears after updating the kernel (or other package, I'm not entirely sure yet) that the microphone on my bluetooth headset no longer is recognized in KDE; the speakers function, but not the microphone. I've extracted some possibly relevant logs.

journalctl -b snippet
May 24 03:30:36 Licht bluetoothd[335]: bluetoothd[335]: Unknown command complete for opcode 19
May 24 03:30:36 Licht bluetoothd[335]: Unknown command complete for opcode 19
May 24 03:30:36 Licht bluetoothd[335]: bluetoothd[335]: Adapter /org/bluez/335/hci0 has been enabled
May 24 03:30:36 Licht bluetoothd[335]: Adapter /org/bluez/335/hci0 has been enabled
...
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
May 23 19:31:19 Licht kernel: cannot submit urb (err = -18)
...
May 23 19:32:53 Licht dbus-daemon[367]: dbus[367]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.36" (uid=1000 pid=1727 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination="
May 23 19:32:53 Licht dbus[367]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.36" (uid=1000 pid=1727 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=3
May 23 19:32:53 Licht dbus[367]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.36" (uid=1000 pid=1727 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=3
May 23 19:32:53 Licht dbus-daemon[367]: dbus[367]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.36" (uid=1000 pid=1727 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination="

systemctl status bluetooth
May 23 19:31:40 Licht bluetoothd[335]: bluetoothd[335]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,1,0,0,0
May 23 19:31:40 Licht bluetoothd[335]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,1,0,0,0
May 23 19:31:42 Licht bluetoothd[335]: bluetoothd[335]: /org/bluez/335/hci0/dev_00_25_02_07_38_38/fd1: fd(24) ready
May 23 19:31:42 Licht bluetoothd[335]: /org/bluez/335/hci0/dev_00_25_02_07_38_38/fd1: fd(24) ready
May 23 19:33:00 Licht bluetoothd[335]: bluetoothd[335]: Badly formated or unrecognized command: AT+BIA=0,0,0,1,1,1,0
May 23 19:33:00 Licht bluetoothd[335]: Badly formated or unrecognized command: AT+BIA=0,0,0,1,1,1,0
May 23 19:33:00 Licht bluetoothd[335]: bluetoothd[335]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,1,0,0,0
May 23 19:33:00 Licht bluetoothd[335]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,1,0,0,0
May 23 19:33:01 Licht bluetoothd[335]: bluetoothd[335]: /org/bluez/335/hci0/dev_00_25_02_07_38_38/fd3: fd(24) ready
May 23 19:33:01 Licht bluetoothd[335]: /org/bluez/335/hci0/dev_00_25_02_07_38_38/fd3: fd(24) ready

Any ideas?

Edit: Added more information

Last edited by jyaworski (2013-05-23 23:44:14)

jyaworski

Member

Registered: 2011-06-20

Posts: 16

Re: Bluetooth: update causes microphone to not function

The issue persists with 3.9.4 as well.

rogorido

Member

Registered: 2009-08-17

Posts: 111

Re: Bluetooth: update causes microphone to not function

Are there any news about this? I have a similar issue with a usb headset. I looked at:
https://bugs.launchpad.net/ubuntu/+sour … ug/1191603
https://bbs.archlinux.org/viewtopic.php?id=167475

but I have kernel 3.10.10 (and have also tried 3.11) and the problem persists...