All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Beckingham <colbec@start.ca>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Bluetooth pulseaudio multiple device entries
Date: Sat, 06 Apr 2013 05:01:16 -0400	[thread overview]
Message-ID: <515FE45C.10908@start.ca> (raw)
In-Reply-To: <CANT-zCW7+n0Jh84T1RSUnP47bf_t5rMQXBByKtegV0E+eM-w9g@mail.gmail.com>



On 04/06/2013 04:05 AM, Mikel Astiz wrote:
> Hi Colin,
>
> On Fri, Apr 5, 2013 at 2:49 PM, Colin Beckingham <colbec@start.ca> wrote:
>>
>>
>> On 04/05/2013 08:16 AM, Mikel Astiz wrote:
>>>
>>> Hi Colin,
>>>
>>> On Fri, Apr 5, 2013 at 1:54 PM, Colin Beckingham <colbec@start.ca> wrote:
>>>>
>>>> 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?
>>>
>>>
>>> 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
>>
>>
>> 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.
>
> 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

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.

-- 
---
Colin Beckingham
613-454-5369
http://www.it4gh.com

  reply	other threads:[~2013-04-06  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 11:54 Bluetooth pulseaudio multiple device entries Colin Beckingham
2013-04-05 12:16 ` Mikel Astiz
2013-04-05 12:49   ` Colin Beckingham
2013-04-06  8:05     ` Mikel Astiz
2013-04-06  9:01       ` Colin Beckingham [this message]
2013-04-06  9:18         ` Mikel Astiz
2013-04-06  9:53           ` Colin Beckingham
2013-04-08 16:39           ` [pulseaudio-discuss] " Tanu Kaskinen
2013-04-08 17:20             ` Colin Beckingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515FE45C.10908@start.ca \
    --to=colbec@start.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz.oss@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.