AudioManager asserts on Connect of BT HFP/A2DP profiles
Description
After boot and clicking Connect in Settings for an already paired BT HFP/A2DP device, I see the following assert which seems to be from the sink name being empty:
Note that the above log occurs when Sink #2 (BT audio gateway) is being processed. It handles Sink #0 and #1 fine, registering them properly. PA sink info follows:
After systemd restarts AudioManager it doesn't crash again, but I get domain errors when it's adding sinks:
Environment
porter board
master build from 8 June
AudioManager logging enabled
To clarify some of the adverse effects of this bug, I should point out that it would result in some sink inputs being left in a muted state. Particularly, this seems to be triggered by bluetooth audio card sink inputs and source outputs and the result is no audio unless the sink input has the mute toggled off. Once the patch is applied, the policy behavior is as expected where these same sink inputs and source outputs are unmuted and uncorked as directed by the default AM configuration present in AGL demo builds.
After boot and clicking Connect in Settings for an already paired BT HFP/A2DP device, I see the following assert which seems to be from the sink name being empty:
Note that the above log occurs when Sink #2 (BT audio gateway) is being processed. It handles Sink #0 and #1 fine, registering them properly. PA sink info follows:
After systemd restarts AudioManager it doesn't crash again, but I get domain errors when it's adding sinks: