Bug 39723

Summary:	The volume limit functionality in alsa-mixer incorrectly assumes non-negative values
Product:	PulseAudio	Reporter:	Tanu Kaskinen <tanuk>
Component:	alsa	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	minor
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Tanu Kaskinen 2011-08-01 10:04:46 UTC

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.

Comment 1 Arun Raghavan 2012-02-08 23:02:43 UTC

Is this something we need to resolve for 2.0?

Comment 2 Tanu Kaskinen 2012-02-08 23:26:50 UTC

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...

Comment 3 GitLab Migration User 2018-07-30 10:34:00 UTC

-- 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.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.