GNOME Bugzilla – Bug 712379
Wizard pairs device but connection is unstable
Last modified: 2013-11-23 19:12:57 UTC
Description: I'm able to pair a device but not use it (connect). Altough I wasn't able to transfer files since the arrival of bluez 5.x and the removal of gvfs-obexftp from the repos, I was able to use my computer as an audio output device when connected with a tablet. Additional info: gnome-bluetooth 3.10.0 gnome-shell 3.10.2 bluez 5-10 openobex 1.7.1 obex-data-server 0.4.6 tablet/phone with android 4.0.3 Steps to reproduce: Pair a phone device, try to connect either from the phone/tablet. See the screencast attached - it appears to connect for a brief moment then the connection is somehow lost.
There's no "audio sink" functionality in the default bluetoothd setup. You'll need to modify your bluetoothd configuration (usually bluetooth.service file) to pass the "-E" (experimental) flag to it.
I just added the -E flag but the connection is lost anyway.
You probably also need a PulseAudio version that handles that. Fedora ships a git snapshot of it to enable that. In any case, gnome-bluetooth doesn't enter anywhere in the picture (just bluetoothd and PulseAudio), so this bug isn't the right avenue to discuss this.
Yes, I installed a pulseaudio git snapshot and it works IF I set up the device via bluetoothctl, but not if I use the bluetooth-wizard to do it, the connection is lost: (setup via bluetooth-wizard): $ bluetoothctl [NEW] Controller 84:4B:F5:DC:11:56 maxwell-0 [default] [NEW] Device 78:1F:DB:08:24:D6 GT-P5100 [bluetooth]# connect 78:1F:DB:08:24:D6 Attempting to connect to 78:1F:DB:08:24:D6 [CHG] Device 78:1F:DB:08:24:D6 Connected: yes Failed to connect: org.bluez.Error.Failed [CHG] Device 78:1F:DB:08:24:D6 Connected: no (setup via bluetoothctl): $ bluetoothctl [NEW] Controller 84:4B:F5:DC:11:56 maxwell-0 [default] [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 84:4B:F5:DC:11:56 Discovering: yes [NEW] Device 78:1F:DB:08:24:D6 GT-P5100 [bluetooth]# pair 78:1F:DB:08:24:D6 Attempting to pair with 78:1F:DB:08:24:D6 [CHG] Device 78:1F:DB:08:24:D6 Connected: yes Request confirmation [agent] Confirm passkey 346266 (yes/no): yes [CHG] Device 78:1F:DB:08:24:D6 Modalias: usb:v000Ap0000d0000 [CHG] Device 78:1F:DB:08:24:D6 UUIDs has unsupported type [CHG] Device 78:1F:DB:08:24:D6 Paired: yes Pairing successful [CHG] Device 78:1F:DB:08:24:D6 Connected: no [bluetooth]# connect 78:1F:DB:08:24:D6 Attempting to connect to 78:1F:DB:08:24:D6 [CHG] Device 78:1F:DB:08:24:D6 Connected: yes Connection successful [CHG] Device 78:1F:DB:08:24:D6 Modalias: usb:v000Ap0000d0000 Discussion
I'm sorry for all the several misguided, useless changes - I was testing several setup/pairing cases. Pulseaudio 4.0 (stable) does not support bluez 5. So far it's not related to gnome-bluetooth at all. However, I am able to connect my device via bluetoothctl and with pulseaudio-git installed. In that case, when I removed the device and tried to set up with bluetooth-wizard, the connection is lost whithin a second either via bluetoothctl or with gnome's bluetooth-properties. That does not happen when I pair my device with bluetoothctl - in this case, connecting the device from bluetooth-preferences work.
(In reply to comment #5) > I'm sorry for all the several misguided, useless changes - I was testing > several setup/pairing cases. Pulseaudio 4.0 (stable) does not support bluez 5. > So far it's not related to gnome-bluetooth at all. However, I am able to > connect my device via bluetoothctl and with pulseaudio-git installed. What exact steps did you take to pair your device using bluetoothctl? > In that > case, when I removed the device and tried to set up with bluetooth-wizard, the > connection is lost whithin a second either via bluetoothctl or with gnome's > bluetooth-properties. That does not happen when I pair my device with > bluetoothctl - in this case, connecting the device from bluetooth-preferences > work. Did the pairing process in gnome-bluetooth ask you to confirm the passkey? What's the output of "info 78:1F:DB:08:24:D6" in "bluetoothctl" after pairing it with gnome-bluetooth, and after pairing it with bluetoothctl?
>What exact steps did you take to pair your device using bluetoothctl? Well using bluetoothclt here are the steps I took (and the info): $ bluetoothctl [NEW] Controller 84:4B:F5:DC:11:56 maxwell-0 [default] [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 84:4B:F5:DC:11:56 Discovering: yes [NEW] Device 78:1F:DB:08:24:D6 GT-P5100 [bluetooth]# pair 78:1F:DB:08:24:D6 Attempting to pair with 78:1F:DB:08:24:D6 [CHG] Device 78:1F:DB:08:24:D6 Connected: yes Request confirmation [agent] Confirm passkey 972781 (yes/no): yes [CHG] Device 78:1F:DB:08:24:D6 Modalias: usb:v000Ap0000d0000 [CHG] Device 78:1F:DB:08:24:D6 UUIDs has unsupported type [CHG] Device 78:1F:DB:08:24:D6 Paired: yes Pairing successful [CHG] Device 78:1F:DB:08:24:D6 Connected: no [bluetooth]# connect 78:1F:DB:08:24:D6 Attempting to connect to 78:1F:DB:08:24:D6 [CHG] Device 78:1F:DB:08:24:D6 Connected: yes Connection successful [CHG] Device 78:1F:DB:08:24:D6 Modalias: usb:v000Ap0000d0000 [bluetooth]# info 78:1F:DB:08:24:D6 Device 78:1F:DB:08:24:D6 Name: GT-P5100 Alias: GT-P5100 Class: 0x5a020c Icon: phone Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: NAP (00001116-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) Modalias: usb:v000Ap0000d0000 > Did the pairing process in gnome-bluetooth ask you to confirm the passkey? Yes, it did. > What's the output of "info 78:1F:DB:08:24:D6" in "bluetoothctl" after pairing > it with gnome-bluetooth, and after pairing it with bluetoothctl? [bluetooth]# info 78:1F:DB:08:24:D6 Device 78:1F:DB:08:24:D6 Name: GT-P5100 Alias: GT-P5100 Class: 0x5a020c Icon: phone Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: NAP (00001116-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) Modalias: usb:v000Ap0000d0000 I've updated the system. Somehow now pairing with the wizard works as expected, the connection isn't lost after 1 second or so - perhaps changes in pulseaudio-git (v4.0.307.ge9d760b-1 as of now) did the trick.
So this is fixed? If so, please close the bug.
No... I tried once more, this time unpairing my computer first from the tablet, and the connection was gone whithin a second.
(In reply to comment #9) > No... I tried once more, this time unpairing my computer first from the tablet, > and the connection was gone whithin a second. At this point, I don't think that I can help more. There's no difference between pairing through using the command-line and through the wizard, so I'm inclined to say that it's a problem in either BlueZ or pulseaudio, and that looking at gnome-bluetooth is a red herring.
*** Bug 714994 has been marked as a duplicate of this bug. ***