Bluetooth pulseaudio multiple device entries

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to crash, but BT and PA are still running and device is working and gnome window can be opened again.

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Hi Colin,

Quoted 21 lines · Colin Beckingham

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to crash, but BT and PA are still running and device is working and gnome window can be opened again.

Quoted 3 lines

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Can you specify which versions of BlueZ and PulseAudio you're using?

Also, please check:
a. which modules are loaded during the issue by doing "pactl list modules" or similar.
b. which bluetooth devices BlueZ registers on D-Bus: "test-device list"/"bluez-test-device list" or similar. You can alternatively use a tool such as d-feet.

Cheers,
Mikel

Quoted 41 lines · Mikel Astiz

Hi Colin,

Quoted 23 lines · Colin Beckingham

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the
list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to crash, but BT and PA are still running and device is working and gnome window can be opened again.

Quoted 3 lines

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Can you specify which versions of BlueZ and PulseAudio you're using?

Also, please check:
a. which modules are loaded during the issue by doing "pactl list modules" or similar.
b. which bluetooth devices BlueZ registers on D-Bus: "test-device list"/"bluez-test-device list" or similar. You can alternatively use a tool such as d-feet.

Quoted 2 lines

Cheers,
Mikel

Mikel -

-----------------

$ pulseaudio --version
pulseaudio 3.0

-------------------

# bluetoothd --version
4.101

-------------------

# test-device list
00:0D:E6:6E:51:47 WEP475

-------------------

# pactl list modules

### this module is added after starting the Samsung device

Module #28

    Name: module-bluetooth-device
    Argument: address="00:0D:E6:6E:51:47"

path="/org/bluez/455/hci0/dev_00_0D_E6_6E_51_47"
Usage counter: 0
Properties:
module.author = "Joao Paulo Rechi Vita" module.description = "Bluetooth audio sink and source" module.version = "3.0"

-------------------

A small point to add to steps to reproduce:

11. with two entries showing in PA, shut down of BT device removes the latest added entry from the PA list leaving one entry for the device even though it is not active.

Hi Colin,

Quoted 81 lines · Colin Beckingham

Quoted 41 lines · Mikel Astiz

Hi Colin,

Quoted 23 lines · Colin Beckingham

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the
list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to crash, but BT and PA are still running and device is working and gnome window can be opened again.

Quoted 3 lines

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Can you specify which versions of BlueZ and PulseAudio you're using?

Also, please check:
a. which modules are loaded during the issue by doing "pactl list modules" or similar.
b. which bluetooth devices BlueZ registers on D-Bus: "test-device list"/"bluez-test-device list" or similar. You can alternatively use a tool such as d-feet.

Quoted 2 lines

Cheers,
Mikel

Mikel -

-----------------

$ pulseaudio --version
pulseaudio 3.0

-------------------

# bluetoothd --version
4.101

-------------------

# test-device list
00:0D:E6:6E:51:47 WEP475

-------------------

# pactl list modules

### this module is added after starting the Samsung device

Module #28

     Name: module-bluetooth-device
     Argument: address="00:0D:E6:6E:51:47"

path="/org/bluez/455/hci0/dev_00_0D_E6_6E_51_47"
Usage counter: 0
Properties:
module.author = "Joao Paulo Rechi Vita" module.description = "Bluetooth audio sink and source" module.version = "3.0"

Quoted 7 lines

-------------------

A small point to add to steps to reproduce:

11. with two entries showing in PA, shut down of BT device removes the latest added entry from the PA list leaving one entry for the device even though it is not active.

As you probably guessed, the traces you provide look good, no duplicated devices there. I would thus assume it's a UI issue, you might confirm this by using pavucontrol and checking whether the card (representing the device) is listed twice or not.

Besides, when you say "7. about 10 sec later a second entry for the same BT device...", is this happening only after you pair the device? Or does the issue also reproduce every time the device gets connected (without unpair + pair)?

Cheers,
Mikel

Quoted 107 lines · Mikel Astiz

Hi Colin,

Quoted 89 lines · Colin Beckingham

Quoted 47 lines · Mikel Astiz

Hi Colin,

Quoted 26 lines · Colin Beckingham

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the
list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to
crash, but BT and PA are still running and device is working and gnome window can be opened again.

Quoted 3 lines

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Can you specify which versions of BlueZ and PulseAudio you're using?

Also, please check:
a. which modules are loaded during the issue by doing "pactl list modules" or similar.
b. which bluetooth devices BlueZ registers on D-Bus: "test-device list"/"bluez-test-device list" or similar. You can alternatively use a tool such as d-feet.

Quoted 2 lines

Cheers,
Mikel

Mikel -

-----------------

$ pulseaudio --version
pulseaudio 3.0

-------------------

# bluetoothd --version
4.101

-------------------

# test-device list
00:0D:E6:6E:51:47 WEP475

-------------------

# pactl list modules

### this module is added after starting the Samsung device

Module #28

     Name: module-bluetooth-device
     Argument: address="00:0D:E6:6E:51:47"

path="/org/bluez/455/hci0/dev_00_0D_E6_6E_51_47"
Usage counter: 0
Properties:
module.author = "Joao Paulo Rechi Vita" module.description = "Bluetooth audio sink and source" module.version = "3.0"

Quoted 7 lines

-------------------

A small point to add to steps to reproduce:

11. with two entries showing in PA, shut down of BT device removes the latest added entry from the PA list leaving one entry for the device even though it is not active.

As you probably guessed, the traces you provide look good, no duplicated devices there. I would thus assume it's a UI issue, you might confirm this by using pavucontrol and checking whether the card (representing the device) is listed twice or not.

Quoted 7 lines

Besides, when you say "7. about 10 sec later a second entry for the same BT device...", is this happening only after you pair the device? Or does the issue also reproduce every time the device gets connected (without unpair + pair)?

Cheers,
Mikel

Thanks Mikel

My testing to this point has been that the device was connected automatically having been pre-registered and paired.

So I deleted the pre-registered entry and re-paired the device. The device entry behaved correctly when first paired, however when I left the registration in place, unconnected the device and then reconnected it, the duplicates reappeared.

In fact each time I selected an entry at random and clicked "test speakers" it created a new entry. At one point I had 6 entries all working and all the same device.

It certainly looks like a UI issue. I will contact the PA folks. Thanks for helping me remove the BT side from the query list.

Hi Colin,

Quoted 129 lines · Colin Beckingham

Quoted 107 lines · Mikel Astiz

Hi Colin,

Quoted 89 lines · Colin Beckingham

Quoted 47 lines · Mikel Astiz

Hi Colin,

Quoted 26 lines · Colin Beckingham

Good day: using Opensuse 12.3 with standard desktop kernel from repo, pulseaudio under Gnome.

Steps to reproduce:
1. clean boot of machine.
2. USB Bluetooth adapter Belkin which works reliably
3. Issue command as root "hciconfig 0 sspmode 0" - this is essential otherwise bluetooth device not recognized.
4. Open gnome sound settings from user menu; onboard sound device is present, only one entry
5. switch on bluetooth device Samsung WEP 475
6. device is recognized and paired, an entry appears in PA list
7. about 10 sec later a second entry for the same BT device appears in the
list
8. after playing with the windows sometimes the second entry will go away
9. at least one of the entries will work and PA shows amplitude changes registering for the input device
10. sometimes clicking the wrong one will cause Gnome settings window to
crash, but BT and PA are still running and device is working and gnome window can be opened again.

Quoted 3 lines

Clearly the multiple entries thing is not normal behaviour. Might be a BT issue, or a PA issue, or a Gnome issue or other. It's a tossup where where to start, can I rule out the BT side?

Can you specify which versions of BlueZ and PulseAudio you're using?

Also, please check:
a. which modules are loaded during the issue by doing "pactl list modules" or similar.
b. which bluetooth devices BlueZ registers on D-Bus: "test-device list"/"bluez-test-device list" or similar. You can alternatively use a tool such as d-feet.

Quoted 2 lines

Cheers,
Mikel

Mikel -

-----------------

$ pulseaudio --version
pulseaudio 3.0

-------------------

# bluetoothd --version
4.101

-------------------

# test-device list
00:0D:E6:6E:51:47 WEP475

-------------------

# pactl list modules

### this module is added after starting the Samsung device

Module #28

      Name: module-bluetooth-device
      Argument: address="00:0D:E6:6E:51:47"

path="/org/bluez/455/hci0/dev_00_0D_E6_6E_51_47"
Usage counter: 0
Properties:
module.author = "Joao Paulo Rechi Vita" module.description = "Bluetooth audio sink and source" module.version = "3.0"

Quoted 7 lines

-------------------

A small point to add to steps to reproduce:

11. with two entries showing in PA, shut down of BT device removes the latest added entry from the PA list leaving one entry for the device even though it is not active.

As you probably guessed, the traces you provide look good, no duplicated devices there. I would thus assume it's a UI issue, you might confirm this by using pavucontrol and checking whether the card (representing the device) is listed twice or not.

Quoted 7 lines

Besides, when you say "7. about 10 sec later a second entry for the same BT device...", is this happening only after you pair the device? Or does the issue also reproduce every time the device gets connected (without unpair + pair)?

Cheers,
Mikel

Thanks Mikel

My testing to this point has been that the device was connected automatically having been pre-registered and paired.

So I deleted the pre-registered entry and re-paired the device. The device entry behaved correctly when first paired, however when I left the registration in place, unconnected the device and then reconnected it, the duplicates reappeared.

Quoted 6 lines

In fact each time I selected an entry at random and clicked "test speakers" it created a new entry. At one point I had 6 entries all working and all the same device.

It certainly looks like a UI issue. I will contact the PA folks. Thanks for helping me remove the BT side from the query list.

[CCing PulseAudio mailing list]

In the PA side, double check that you don't have duplicated instances of module-bluetooth-device. There was an issue
(https://bugs.freedesktop.org/show_bug.cgi?id=57239) similar to the one you describe, which should have been fixed for 3.0 (commit 41055145d7563c20fd58ed4b0a9b349c2363bb02).

Quoted 8 lines

My testing to this point has been that the device was connected automatically having been pre-registered and paired.

So I deleted the pre-registered entry and re-paired the device. The device entry behaved correctly when first paired, however when I left the registration in place, unconnected the device and then reconnected it, the duplicates reappeared.

Quoted 6 lines

In fact each time I selected an entry at random and clicked "test speakers" it created a new entry. At one point I had 6 entries all working and all the same device.

It certainly looks like a UI issue. I will contact the PA folks. Thanks for helping me remove the BT side from the query list.

Quoted 13 lines · Colin Beckingham

Quoted 12 lines

My testing to this point has been that the device was connected automatically having been pre-registered and paired.

So I deleted the pre-registered entry and re-paired the device. The device entry behaved correctly when first paired, however when I left the registration in place, unconnected the device and then reconnected it, the duplicates reappeared.

In fact each time I selected an entry at random and clicked "test speakers" it created a new entry. At one point I had 6 entries all working and all the same device.

Quoted 2 lines

Quoted 2 lines

It certainly looks like a UI issue. I will contact the PA folks. Thanks for helping me remove the BT side from the query list.

You can check if the bug is in the UI or in PulseAudio by running "pactl list cards short" and "pactl list sinks short". I that shows multiple entries for the same device, it's not a UI bug.

Is the UI that you're using pavucontrol or something else?