GNOME Bugzilla – Bug 300375
SB Live! mixer does not show AC97 capture option, breaking capture
Last modified: 2011-01-27 04:45:53 UTC
Version details: gnome-media-2.10.0-2 Distribution/Version: FC4t2 I have a SB Live! value, lspci -n gives 02:03.0 Class 0401: 1102:0002 (rev 07) I'm using Fedora Core 4 test release 2, kernel-2.6.11-1.1234_FC4. Finally the ALSA settings come as something sane, so I can hear sound after installation without unmuting everything, but microphone capture didn't work. After checking out ALSA documentation, I set it up properly using alsamixer, as gnome-volume-control a) didn't show AC97 capture slider and b) had it muted. While there are two AC97 options in the many choices in properties for the mixer both make the AC97 input slider show up, but neither shows the AC97 capture slider appear, even when both are checked. It would be nice if the capture worked out of the box, but Gnome-volume-control absolutely should show the AC97 capture slider.
A little further experimentation has revealed that actually what's happening is that both AC97 checkboxes create the AC97 capture slider, but in the Playback tab. The AC97 playback slider is not created in either.
Ubuntu bug about that: https://launchpad.net/products/gnome-media/+bug/35050 "The Mixer applet does not show the Capture slider by default. By default this slider is down, so sound recording does not work at all. For novice users it is difficult to find out why recording does not work, then. I think the Capture slider should be on by default and it should be to 100% level (maybe label it Recording level or something). This is a wish I have for better Ubuntu usability. Thanks."
Aaron, I guess this bug is still reproducible, can you please check with a more recent version or trunk? Sebastien, the LaunchPad bug is about "Capture" slider and default value/settings (which is handle in a different place in debian/ubuntu, during init, iirc). i think this bug is mainly about "AC97 capture" (on SB Live)
This bug does still reproduce?
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.32.1 or later, thanks.