Description of problem: Logitech Quickcam pro 9000 mic is not working with pulseaudio. I looked at the pulse audio volume control and I can see my quickcam under the Configuration tab and it is set to Analog mono audio input. Then, I started skype call testing but I can't see anything under the "Input Devices" tab when it shows "All Except Monitors". Version-Release number of selected component (if applicable): pulseaudio-libs-zeroconf-0.9.21-4.fc12.x86_64 pulseaudio-module-gconf-0.9.21-4.fc12.x86_64 alsa-plugins-pulseaudio-1.0.22-1.fc12.x86_64 pulseaudio-0.9.21-4.fc12.x86_64 pulseaudio-module-bluetooth-0.9.21-4.fc12.x86_64 alsa-plugins-pulseaudio-1.0.22-1.fc12.i686 pulseaudio-libs-glib2-0.9.21-4.fc12.x86_64 pulseaudio-utils-0.9.21-4.fc12.x86_64 pulseaudio-module-zeroconf-0.9.21-4.fc12.x86_64 pulseaudio-esound-compat-0.9.21-4.fc12.x86_64 pulseaudio-libs-0.9.21-4.fc12.i686 pulseaudio-libs-0.9.21-4.fc12.x86_64 pulseaudio-libs-glib2-0.9.21-4.fc12.i686 How reproducible: Start Skype and run a test call. Steps to Reproduce: 1. 2. 3. Actual results: No audio input from the mic, but the video is working. Expected results: Additional info:
Created attachment 394802 [details] lsmod
Created attachment 394803 [details] lspci
Created attachment 394804 [details] lsusb
And, does g-v-c show it in the "Inputs" tab?
I am using KDE. The KMix shows the Logitech Quickcam pro 9000 mic and it is captured.
Yeah, well I have no clue about KDE. Does gnome-volume-control show it in the "Inputs tab?
OK. I just install gnome-media. I can't see anything under gnome-volume-control "Inputs" tab but I see the device under "Hardware" tab.
Please run a "pulseaudio -vvvvvv" in a terminal (disable autospawning first by setting autospawn=no in ~/.pulse/client.conf, and terminate the running PA instance then by issuing pulseaudio -k), and paste the startup output this generates here.
Created attachment 395014 [details] pulseaudio output pulseaudio -vvvvvv
I put the output in an attachment. Let me know if I need to do other steps. Thanks
Created attachment 395015 [details] pulse audio output
The interesting part is this: W: alsa-util.c: Unable to set sw params: No such device E: alsa-source.c: Failed to set software parameters: No such device This message is generated if ALSA's snd_pcm_sw_params() returns -ENODEV, after snd_pcm_hw_param() and setting the individual parameters worked fine. This shouldn't normally happen. I don't see why the driver returns -ENODEV here. What makes me really wonder is what is going on with these these lines however: D: alsa-util.c: Managed to open hw:0 D: alsa-util.c: Maximum hw buffer size is 32768 ms D: alsa-util.c: Set buffer size first (to 638 samples), period size second (to 79 samples). D: alsa-util.c: Managed to open front:1 D: alsa-util.c: Maximum hw buffer size is 23777 ms D: alsa-util.c: Set buffer size first (to 1760 samples), period size second (to 220 samples). These are extremely short fragments. That should not happen. You apparently have disabled tsched. Did you also fiddle with the fragment settings i default.pa? If you enabled tsched, does the problem go away?
Thank Lennart. I re-enabled the tsched and the mic is working again. I also had the fragment size set to 5ms. Both changes were done to improve sound quality on Virtual Box. I guess I would rather have the mic than good audio in virtual box.
So I tracked this down to snd_pcm_sw_params_set_period_event(pcm, swparams, 1) which will cause a subsequent snd_pcm_sw_param() to fail on a few devices, such as the Logitech webcams. Most other devices eat this without problems. I don't really see why this could be a reason for failure since the period event is enabled anyway by default. This really looks a bug in alsa to me, hence reassigning.
This patch should solve this issue: http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=f1713475087027925358c3f9dd3db70723ed8d11 I will update alsa-lib packages ASAP.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.