From: Tanu Kaskinen <tanuk@iki.fi>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: Colin Beckingham <colbec@start.ca>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>
Subject: Re: [pulseaudio-discuss] Bluetooth pulseaudio multiple device entries
Date: Mon, 08 Apr 2013 19:39:57 +0300 [thread overview]
Message-ID: <1365439197.3683.52.camel@laptop> (raw)
In-Reply-To: <CANT-zCW3fMvHN_Ga0n6N8Kg7Qq2bQyxT_fidkCT201UeCXaD5g@mail.gmail.com>
> On Sat, Apr 6, 2013 at 11:01 AM, Colin Beckingham <colbec@start.ca> wrote:
> > 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.
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?
--
Tanu
next prev parent reply other threads:[~2013-04-08 16:39 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
2013-04-06 9:18 ` Mikel Astiz
2013-04-06 9:53 ` Colin Beckingham
2013-04-08 16:39 ` Tanu Kaskinen [this message]
2013-04-08 17:20 ` [pulseaudio-discuss] " 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=1365439197.3683.52.camel@laptop \
--to=tanuk@iki.fi \
--cc=colbec@start.ca \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@gmail.com \
--cc=pulseaudio-discuss@lists.freedesktop.org \
/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.