The configuration file seems to be parsed correctly, but in other places in alsa-mixer.c negative volume limit values are treated as if they would signify that no volume limit has been set. There should be a separate boolean variable, "volume_limit_set", for determining whether a limit has been configured.
Is this something we need to resolve for 2.0?
The volume limit feature is not used much, and negative volumes from alsa are rare, so I'd say this is not something that we *need* to fix for 2.0. Fixing this should be quite easy, though...
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/506.