alsa ucm: do not assign JackHWMute when JackControl is missing for the UCM device
authorJaroslav Kysela <perex@perex.cz>
Sun, 1 Mar 2020 14:55:07 +0000 (15:55 +0100)
committerJaroslav Kysela <perex@perex.cz>
Sun, 1 Mar 2020 14:55:37 +0000 (15:55 +0100)
Fixes: https://github.com/alsa-project/alsa-ucm-conf/issues/14
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
src/modules/alsa/alsa-ucm.c

index b7d2c5b9c51aee5b50e801ef4141cf9a658f5a44..8df24e7b51d7be97daccddeed27cf4d50d5be3d0 100644 (file)
@@ -1730,6 +1730,10 @@ static int ucm_create_profile(
         /* JackHWMute contains a list of device names. Each listed device must
          * be associated with the jack object that we just created. */
         jack_hw_mute = pa_proplist_gets(dev->proplist, PA_ALSA_PROP_UCM_JACK_HW_MUTE);
+        if (jack_hw_mute && !jack) {
+            pa_log("[%s] JackHWMute set, but JackControl is missing", name);
+            jack_hw_mute = NULL;
+        }
         if (jack_hw_mute) {
             char *hw_mute_device_name;
             const char *state = NULL;