FS#37452 - [bluedevil] Bluetooth headset does not work in KDE after the update to bluez 5.x
Attached to Project:
Arch Linux
Opened by Andrej Podzimek (andrej) - Tuesday, 22 October 2013, 19:35 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 21 December 2013, 17:38 GMT
Opened by Andrej Podzimek (andrej) - Tuesday, 22 October 2013, 19:35 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 21 December 2013, 17:38 GMT
|
Details
Description:
Creative WP-300 headste stopped working after the update to bluez 5. My bluetooth mouse still works (with an extremely long re-connection delay though). The WP-300 headset could not be used based on the old pairing metadata inherited from bluez 4.x, because bluedevil-audio in KDE received signal 11. Removing the device and pairing it again does not work either (timeout). The headset appears on the scan output, but cannot be paired from KDE. Additional info: * package version(s) bluedevil 2.0-0.1 bluez 5.9-1 bluez-firmware 1.2-7 bluez-libs 5.9-1 bluez-utils 5.9-1 libbluedevil 2.0-0.1 pulseaudio 4.0-2 pulseaudio-alsa 2-2 * config and/or log files etc. There are *no* error reports in journalctl -u bluetooth. Steps to reproduce: Try to use/pair a Bluetooth headset with bluez 5 in KDE (preferably one without a microphone, but I'm not sure whether this is relevant). |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Saturday, 21 December 2013, 17:38 GMT
Reason for closing: Fixed
Additional comments about closing: bluedevil 1:2.0rc1-1
Saturday, 21 December 2013, 17:38 GMT
Reason for closing: Fixed
Additional comments about closing: bluedevil 1:2.0rc1-1
https://bugs.archlinux.org/task/37347?project=1&order=dateopened&sort=desc&pagenum=2
Application: Bluetooth Audio Helper (bluedevil-audio), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#5 0x00007ffcd4e40fed in BlueDevil::Device::isPaired() const () from /usr/lib/libbluedevil.so.2
#6 0x0000000000402d2e in _start ()
Seems libbluedevil is to blame.
Strange thing is that I can't find bluetoothctl command that should be installed with bluez.
Is package complete ?
@Eric: bluetoothctl is part of bluez-utils, nozt bluez
Using bluetoothctl from a terminal to connect works perfectly.
bluedevil bluez5 support is under the bluez5 branch: http://quickgit.kde.org/?p=bluedevil.git&a=shortlog&h=3a7a27e73e1bc6d65381f8dd7d2a091f544faa32
Application: Bluetooth Audio Helper (bluedevil-audio), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#5 0x00007fc215c64fed in BlueDevil::Device::isPaired() const () from /usr/lib/libbluedevil.so.2
#6 0x0000000000402d2e in _start ()
Should libbluedevil be updated too?
gene
Edit:
OK, I was too quick on this. Just recall I did the pairing using bluetoothctl from the commandline. Trying to pair via the bluedevil-wizard isn't working - crashing. However once paired and trusted i can connect to the headset via the bluedevil systray. The bluedevil audio helper process occasionally crash though, but it does get the connection up.
The bluedevil applet doesn't work, so bluetoothctl is the only option. Unfortunately bluetoothctl connect won't work, so the only working way to make the mouse usable for a while is the following:
0) Set this in bluetoothctl:
pairable on
discoverable on
scan on
None of these ^^^ options is really necessary, but it seems to me that at least some of these options reduce the number of unsuccessful iterations mentioned in 2) below.
1) Switch the mouse to the pairing mode (blue LED blinking or the like)
2) Repeat this...
pair <Bluetooth address>
connect <Bluetooth address>
...until the mouse starts working. You may have to repeat that 5 times or even more. :-(
3) When you let the mouse go into a deeper sleep state (i.e., you don't use it for an hour or the like), you have to repeat everything again from point 0).
Well, this bug is somewhat frustrating. :-D
You should provide btmon and bluetoothd logs.
I have similar issues wit my devices but haven't found time to report it so far.
Anyway bluetoothctl issues are not bluedevil related and somewhat offtopic here.
I can connect to my headset using bluetoothctl and the instructions on the wiki[1] in KDE, but not using Bluedevil. My microphone doesn't work (it doesn't even show up in bluetoothctl), but that appears to be on bluez and not bluedevil.
https://wiki.archlinux.org/index.php/Bluetooth_Headset
- Logitech diNovo kbd - OK
- Logitech MX1000 mouse - OK
- Cheapo Bluetooth Headset - OK (using pulseaudio-git)
- Random BT Audio Receiver #1 and #2 - works but sometimes need a manual bluetoothctl connect command
To pair and trust a new device, I need to do the following:
$ bluetoothctl
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
# Power on device here in pairing mode...
[NEW] Device 00:02:5B:01:3B:B1 SX-907C (a headset)
Request PIN code
[agent] Enter PIN code: 0000
[CHG] Device 00:02:5B:01:3B:B1 UUIDs has unsupported type
Authorize service
[CHG] Device 00:02:5B:01:3B:B1 UUIDs has unsupported type
[CHG] Device 00:02:5B:01:3B:B1 Paired: yes
[agent] Authorize service 0000110d-0000-1000-8000-00805f9b34fb (yes/no): yes
[CHG] Device 00:02:5B:01:3B:B1 UUIDs has unsupported type
Authorize service
[agent] Authorize service 0000110c-0000-1000-8000-00805f9b34fb (yes/no): yes
[bluetooth]# trust 00:02:5B:01:3B:B1
[CHG] Device 00:02:5B:01:3B:B1 Trusted: yes
Changing 00:02:5B:01:3B:B1 trust succeeded
[bluetooth]# connect 00:02:5B:01:3B:B1
[bluetooth]# quit
this works with pulseaudio from the repos as well. Just connected my headset again (after deinstalling libbluedevil and bluedevil from my system)
Just install bluedevil1 this will install the previous version of bluedevil - which works.
Well this is the case on Manjaro. Unfortunatley Manajaro guys relised that.