Can't select bluetooth input while on a2dp profile

Ok, so one finding:

This row (in gvc-mixer-control.c, update_sink and update_source)
                control->priv->profile_swapping_device_id = GVC_MIXER_UI_DEVICE_INVALID;

...needs to move inside this block:
                         if (gvc_mixer_ui_device_get_stream_id (dev) == gvc_mixer_stream_get_id (stream)) {

...otherwise profile_swapping_device_id gets forgotten before it is used.

Ok, and the second finding. If a stream is currently creating, pa_stream_disconnect fails, and the stream continues to set itself up and starts to produce samples.
So when the sound applet starts up, this seems to happen due to some race condition because active_input_update is called twice.

There are more than one way to solve this problem, and maybe I should do both workarounds:

 1) If pa_stream_disconnect fails, make sure that we retry the disconnection later.

 2) If active_input_update is called twice for the same object, there is no need to tear down the stream and then set it up again. This is what seems to happen at startup.

First bug upstreamed as https://bugzilla.gnome.org/show_bug.cgi?id=736943

This bug was fixed in the package unity-control-center - 14.10.0+14.10.20140922-0ubuntu1

---------------
unity-control-center (14.10.0+14.10.20140922-0ubuntu1) utopic; urgency=low

  [ Robert Ancell ]
  * Fix Vcs-Bzr link that was pointing to gnome-control-center packaging
  * Use libunity-settings-daemon to replace functionality that is being
    changed/removed in libgnome-desktop (LP: #1372240)

  [ David Henningsson ]
  * Make sure selecting a bluetooth input works even when the headset is
    in A2DP mode, and make sure the correct levels are shown in the
    level bar (Bug 1367693) (LP: #1367693)

  [ Mathieu Trudel-Lapierre ]
  * Deactivate the wired device when wired is switched off. (LP:
    #1354987)
 -- Ubuntu daily release <email address hidden> Mon, 22 Sep 2014 11:36:24 +0000

Hello David, or anyone else affected,

Accepted unity-control-center into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity-control-center/14.04.3+14.04.20140922-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Confirmed working on my laptop (which was the one where I also did the development of the patch).

Also, I ran a "random clicking" regression test on my desktop computer (which does not have bluetooth), no regressions found.

This bug was fixed in the package unity-control-center - 14.04.3+14.04.20140922-0ubuntu1

---------------
unity-control-center (14.04.3+14.04.20140922-0ubuntu1) trusty; urgency=low

  [ David Henningsson ]
  * Make sure selecting a bluetooth input works even when the headset is
    in A2DP mode, and make sure the correct levels are shown in the
    level bar (Bug 1367693) (LP: #1367693)
 -- Ubuntu daily release <email address hidden> Mon, 22 Sep 2014 17:27:43 +0000

The verification of the Stable Release Update for unity-control-center has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.