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 86783 - Switching record source in the volume control doesn't work
Switching record source in the volume control doesn't work
Status: RESOLVED FIXED
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.0.x
Other Linux
: Normal major
: ---
Assigned To: Iain
gnome media maintainers
: 103289 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-28 22:36 UTC by Ilya
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for gmix.c (278 bytes, patch)
2002-06-28 22:40 UTC, Ilya 		none Details | Review

Description Ilya 2002-06-28 22:36:58 UTC 
The record source switching in the volume control doesn't work. I've found
the problem and will attach a patch.
Sorry if it has been already fixed, I can't find link to CVS on the GNOME site.
Comment 1 Ilya 2002-06-28 22:40:27 UTC 
Created attachment 9503 [details] [review]
Patch for gmix.c
Comment 2 Ilya 2002-06-28 23:05:44 UTC 
OK, foolish me have found the CVS now, but the bug is still here,  see
the patch.
Comment 3 Luis Villa 2002-07-02 05:14:31 UTC 
Adding PATCH keyword and marking major.
Comment 4 Jeremy Nickurak 2002-07-26 05:29:24 UTC 
Would this be the same problem that prevents gnome-volume-control from
letting me configure play/record settings for my line-in, while aumix
works fine? (Eg, pressing space to toggle play/record on line-in in
aumix works fine, however upon running gnome-volume-control, line-in
is immediately silenced, and toggling line-in's checkboxes in
gnome-volume-control makes no difference)
Comment 5 Iain 2002-08-03 00:18:05 UTC 
Fixed in CVS.

Jeremy, yes, quite possibly. could you check if it works now?

Thanks guys
Comment 6 Luis Villa 2003-07-11 02:16:34 UTC 
*** Bug 103289 has been marked as a duplicate of this bug. ***