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 678681 - Alert Sound doesn't work if you drag volume to minimum and then to another position
Alert Sound doesn't work if you drag volume to minimum and then to another po...
Status: RESOLVED DUPLICATE of bug 677478
Product: gnome-control-center
Classification: Core
Component: Sound
3.4.x
Other Linux
: Normal minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-23 21:38 UTC by Sergio Benjamim
Modified: 2012-06-25 18:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sergio Benjamim 2012-06-23 21:38:33 UTC
The alert sound doesn't work if you drag the alert volume to minimum and after that you drag out the control to another position. It only works again if you mute and unmute the alert volume. Take a look on this video:

http://www.youtube.com/watch?v=dIw7jZoWxiU
Comment 1 Sergio Benjamim 2012-06-23 21:57:35 UTC
The last video was made on GNOME Shell (Ubuntu 12.04), I noticed that the same issue happens on Unity 5.12.0. I made another video, in Unity:

http://www.youtube.com/watch?v=WqTmLzO1oL0
Comment 2 André Klapper 2012-06-25 09:16:08 UTC
Did you file a bug report in Ubuntu's bugtracker about it and were asked to upstream it here, after it has been identified as not being due to Ubuntu downstream patches?
Comment 3 Bastien Nocera 2012-06-25 16:03:36 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 677478 ***
Comment 4 Sergio Benjamim 2012-06-25 18:58:06 UTC
It happens in Arch Linux too (since gnome shell 3.0), so I thought it was a upstream problem. I didn't see this bug existed. Thanks for all.