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 587231 - gnome-volume-control doesn't work (almost) at all
gnome-volume-control doesn't work (almost) at all
Status: RESOLVED DUPLICATE of bug 564311
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.26.x
Other All
: Normal blocker
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-28 22:07 UTC by Felipe Lessa
Modified: 2010-01-05 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Felipe Lessa 2009-06-28 22:07:39 UTC 
Please describe the problem:
This report is coming upstream from Gentoo, where I reported it with details.  Please see http://bugs.gentoo.org/show_bug.cgi?id=274819 .

Thanks!

Steps to reproduce:
a. Try to change the volume use gnome-volume-control-applet.

-OR-

b. Try to change the volume using a keybiding.

By "change the volume" I mean increment, decrement or mute.


Actual results:
For b, nothing. For a, it changes but only if the current PA instance is the same that was running when g-v-c-a was started (i.e. 'pulseaudio -k; pulseaudio -D' won't let g-v-c-a work anymore).

Expected results:
Changes in volume :).

Does this happen every time?
Yes.

Other information:
Please see the Gentoo bug.
Comment 1 Bastien Nocera 2009-06-28 23:20:43 UTC 
a) is a dupe of an existing bug (bug 564311)
b) is very unhelpful. There's a debug mode, use it.

Put all the details in the bugzilla, we shouldn't have to go and read bug reports in other bug trackers.
Comment 2 Tobias Mueller 2010-01-05 16:27:58 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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