After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 407313 - Volume does not reach zero when scolling all the way to the bottom
Volume does not reach zero when scolling all the way to the bottom
Status: RESOLVED DUPLICATE of bug 319139
Product: gnome-applets
Classification: Other
Component: mixer
2.16.x
Other All
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-13 02:41 UTC by Taylor Braun-Jones
Modified: 2007-03-11 00:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Taylor Braun-Jones 2007-02-13 02:41:22 UTC
Please describe the problem:
When scrolling the wheel over the volume control applet the volume output from the speakers does not reach zero despite the on screen feedback indicating "Master: muted"

On a similar note, but more of a feature request, it would be nice if the volume increments per mouse scroll were smaller the lower the volume is. The reason being that there is a more perceptive difference between 3% and 6% than there is between 90% and 93%. Perhaps the percentages can still show 3% increments, but the underlying volume will actually be adjusted on some kind of log scale...

Steps to reproduce:
1. With the volume starting at, say, 12%, scroll the mouse wheel down while hoovering over the volume control applet until the volume reaches "Master: muted" instead of a telling you a percentage.


Actual results:
The volume from the speakers is slightly lower than the volume at 3%

Expected results:
The there should be no audio output (*zero* percent)

Does this happen every time?
Yes.

Other information:
Comment 1 Ronald Bultje 2007-03-11 00:59:15 UTC
Crap, wrong button, sorry.
Comment 2 Ronald Bultje 2007-03-11 00:59:28 UTC

*** This bug has been marked as a duplicate of 319139 ***