Description of problem:
Using PA, I can enable mic capture under the settings tab, but I can't disable
it. Immediately after the box goes unchecked, it is checked again.
Version-Release number of selected component (if applicable):
Sorry, I meant the "Switches" tab. To see it, go to Preferences and check the
box next to "Microphone Capture".
so... the "Capture" checkbox in Preferences might be the one that's *actually*
Lennart, does pulseaudio muck about with the capture status for input tracks?
Zack, can you reproduce without pulseaudio running?
Created attachment 208741 [details]
Here's a screenshot, for clarification...
Any special way I need to disable PA?
"killall -9 pulseaudio" will do.
After killing pulseaudio, I can still reproduce this.
(In reply to comment #6)
> "killall -9 pulseaudio" will do.
Not so rude! ;-)
A friendly "pactl exit" should do the same.
(In reply to comment #3)
> Lennart, does pulseaudio muck about with the capture status for input tracks?
> Zack, can you reproduce without pulseaudio running?
PA doesn't fiddle with the capture source controls in ALSA. All it does is
monitoring the ALSA volume scales. And it doesn't even set those, except the
user explicitly asks for it.
I am quite sure that PA is not the culprit here.
Zack, does toggling the same control in alsamixer work?
(gnome-volume-control has some ugly hacks to change the mute control when volume
is set to 0 - maybe it does the same ugly hack for controlling the record input
source? Just a wild guess...)
I can reproduce that on my desktop machine.
I can't *find* the same control with alsamixer.
(In reply to comment #11)
> I can't *find* the same control with alsamixer.
That's because it's a way to mute/disable the input. gnome-volume-control will
show both a switch and a track slider.
Press tab in alsamixer to see the "Mic" track.
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.
If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)
Thanks for your help and we apologize for the interruption.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.