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 600017 - Muting makes the sliders out of sync
Muting makes the sliders out of sync
Status: RESOLVED DUPLICATE of bug 599663
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-29 11:56 UTC by Kamil Páral
Modified: 2010-02-03 11:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bug demonstration video (309.33 KB, video/ogg)
2009-10-29 11:56 UTC, Kamil Páral
Details

Description Kamil Páral 2009-10-29 11:56:04 UTC
Created attachment 146496 [details]
bug demonstration video

In gnome-panel applet, moving the slider to bottom mutes the sound, moving it
up unmutes the sound. In gnome-volume-control moving the slider to left mutes
the sound, moving it right does *not* unmute the sound.

When sound is mutes, slider in gnome-panel applet and slider in g-v-c are out
of sync. Moving slider in applet syncs the sliders again, but only after mouse
release. Moving slider in g-v-c does not sync the sliders at all.

Please see attached screencast.

gnome-media-2.28.1-3.fc12.x86_64
pulseaudio-0.9.19-1.fc12.x86_64
Fedora 12 Rawhide
Comment 1 Bastien Nocera 2009-10-29 12:07:12 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 599663 ***
Comment 2 Kamil Páral 2009-10-29 12:55:36 UTC
I don't this it is a duplicate. This report is about two things:
1. applet slider is behaving differently then g-v-c dialog slider when trying to unmute sound -- that is a duplicate, correct
2. the sliders fall out of sync when mute is enabled -- that is an unresolved issue

It is really weird when you see one volume slider having being at 50% and second being at 0%, and they should have been the same sliders (output volume). Also usually the volume is changed while (during) dragging the applet slider. When the sound is muted through g-v-c, the applet slider does nothing until mouse release (which can cause a sudden burst of loud sound). Is that really intentional? I doubt that.

On top of that, all two issues were not present in gnome-media 2.27.91, it's a regression.

Unfortunately I don't know how this issue can be solved if you insist on notabug for the first one (which I don't see as a good solution, I will comment to that original report on that).
Comment 3 Bastien Nocera 2010-02-03 11:52:48 UTC
(In reply to comment #2)
> I don't this it is a duplicate. This report is about two things:
> 1. applet slider is behaving differently then g-v-c dialog slider when trying
> to unmute sound -- that is a duplicate, correct
> 2. the sliders fall out of sync when mute is enabled -- that is an unresolved
> issue
> 
> It is really weird when you see one volume slider having being at 50% and
> second being at 0%, and they should have been the same sliders (output volume).

One shows a mute checkbox, and not the other one. The applet also has the problem that it's space-constrained.

> Also usually the volume is changed while (during) dragging the applet slider.
> When the sound is muted through g-v-c, the applet slider does nothing until
> mouse release (which can cause a sudden burst of loud sound). Is that really
> intentional? I doubt that.

It is intentional, although I'll be changing that as part of bug 602203.

> On top of that, all two issues were not present in gnome-media 2.27.91, it's a
> regression.
> 
> Unfortunately I don't know how this issue can be solved if you insist on
> notabug for the first one (which I don't see as a good solution, I will comment
> to that original report on that).

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