Description of problem: I've just bought Gembird AP-5.1 which, according to a quick Google, should be supported in Linux, so I thought it's a safe bet ... Kernel sees that as: [66169.134725] usb 2-1.2: new full-speed USB device number 3 using ehci-pci [66169.220729] usb 2-1.2: New USB device found, idVendor=0d8c, idProduct=000c [66169.220739] usb 2-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [66169.220745] usb 2-1.2: Product: C-Media USB Headphone Set [66169.223726] input: C-Media USB Headphone Set as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/input/input17 [66169.224503] hid-generic 0003:0D8C:000C.0002: input,hidraw1: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-0000:00:1d.0-1.2/input3 [66170.501337] ALSA sound/usb/mixer.c:931 13:0: cannot get min/max values for control 2 (id 13) [66170.501355] ALSA sound/usb/mixer.c:931 9:0: cannot get min/max values for control 2 (id 9) [66170.501364] ALSA sound/usb/mixer.c:931 10:0: cannot get min/max values for control 2 (id 10) [66170.501889] usbcore: registered new interface driver snd-usb-audio Now trying to play something, the sound still comes from my laptop's internal speakers. Trying to use the controls on the cable, it influences volume of the internal speakers. Version-Release number of selected component (if applicable): pulseaudio-2.1-6.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. buy Gembird AP-5.1 (other headsets may fail as well ...), connect it to a computer that has internal soundcard 2. try to play some sound, e.g. open a browser and play someting on youtube 3. try the buttons on the headset's cable Actual results: 2. sound comes through the internal soundcard 3. the buttons affect volume of the internal soundcard Expected results: 2. sound comes from the headset 3. the buttons on the cable affect volume set for the headset Additional info: mplayer -ao alsa:device=hw=1.0 ... sends sound to the headset without any problem trying to google, it seems this can be worked around by writing some custom udev rules ... well, that's not exactly what I'd expect if someone says things like "the main advantage of pulseaudio is that it works out of the box" in various contexts
Same problem here with a "Trust Mauro USB Headset": failing with ALSA sound/usb/mixer.c:929 9:0: cannot get min/max values for control 2 dmesg ... [ 1570.395178] usb 3-2: USB disconnect, device number 4 [ 2919.672695] usb 3-1: new full-speed USB device number 5 using xhci_hcd [ 2919.684506] usb 3-1: New USB device found, idVendor=05e1, idProduct=2010 [ 2919.684520] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 2919.684528] usb 3-1: Product: USB VoIP Device [ 2919.688360] ALSA sound/usb/mixer.c:929 9:0: cannot get min/max values for control 2 (id 9) [ 2919.688378] ALSA sound/usb/mixer.c:929 10:0: cannot get min/max values for control 2 (id 10) [ 2919.692015] input: USB VoIP Device as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.3/input/input14 [ 2919.692780] hid-generic 0003:05E1:2010.0006: input,hidraw0: USB HID v1.00 Device [USB VoIP Device] on usb-0000:00:14.0-1/input3 NOTE - it works on the same laptop (!) when booting Ubuntu: Interestingly, when I boot with a Ubuntu USB installation, the headset works out of the box (alsa 1.0.25+dfsg-0ubuntu1.1, pulsaudio 1:1.1-0ubuntu15.2, kernel 3.5.0-26-generic). System: ASUS S200E notebook uname -a Linux oboe.localdomain 3.8.4-202.fc18.x86_64 #1 SMP Thu Mar 21 17:02:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci|grep Audio 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) lsusb -v ... see attachment "lsusb_output.txt" In ALSA, the headset shows up as ARCTIC Sound P261 Headphones rpm -qa | grep -E 'alsa|pulse|gstreamer' | sort alsa-firmware-1.0.25-2.fc18.noarch alsa-lib-1.0.26-2.fc18.i686 alsa-lib-1.0.26-2.fc18.x86_64 alsa-plugins-pulseaudio-1.0.26-2.fc18.x86_64 alsa-tools-firmware-1.0.26.1-1.fc18.x86_64 alsa-utils-1.0.26-1.fc18.x86_64 gstreamer-0.10.36-2.fc18.i686 gstreamer-0.10.36-2.fc18.x86_64 gstreamer1-1.0.7-1.fc18.x86_64 gstreamer1-libav-1.0.6-1.fc18.x86_64 gstreamer1-plugins-bad-free-1.0.7-1.fc18.x86_64 gstreamer1-plugins-bad-freeworld-1.0.6-1.fc18.x86_64 gstreamer1-plugins-base-1.0.7-1.fc18.x86_64 gstreamer1-plugins-good-1.0.7-1.fc18.x86_64 gstreamer1-plugins-ugly-1.0.6-1.fc18.x86_64 gstreamer-ffmpeg-0.10.13-8.fc18.x86_64 gstreamer-plugins-bad-free-0.10.23-13.fc18.i686 gstreamer-plugins-bad-free-0.10.23-13.fc18.x86_64 gstreamer-plugins-base-0.10.36-3.fc18.i686 gstreamer-plugins-base-0.10.36-3.fc18.x86_64 gstreamer-plugins-espeak-0.4.0-1.fc18.x86_64 gstreamer-plugins-good-0.10.31-5.fc18.x86_64 gstreamer-plugins-ugly-0.10.19-5.fc18.x86_64 gstreamer-tools-0.10.36-2.fc18.x86_64 PackageKit-gstreamer-plugin-0.8.9-1.fc18.x86_64 phonon-backend-gstreamer-4.6.3-1.fc18.x86_64 pulseaudio-2.1-6.fc18.x86_64 pulseaudio-libs-2.1-6.fc18.i686 pulseaudio-libs-2.1-6.fc18.x86_64 pulseaudio-libs-glib2-2.1-6.fc18.x86_64 pulseaudio-module-x11-2.1-6.fc18.x86_64 pulseaudio-utils-2.1-6.fc18.x86_64 ls -al /dev/snd total 0 drwxr-xr-x. 4 root root 300 Jul 14 11:01 ./ drwxr-xr-x. 20 root root 3580 Jul 14 11:01 ../ drwxr-xr-x. 2 root root 60 Jul 14 11:01 by-id/ drwxr-xr-x. 2 root root 80 Jul 14 11:01 by-path/ crw-rw----+ 1 root audio 116, 7 Jul 14 2013 controlC0 crw-rw----+ 1 root audio 116, 10 Jul 14 11:01 controlC1 crw-rw----+ 1 root audio 116, 6 Jul 14 2013 hwC0D0 crw-rw----+ 1 root audio 116, 5 Jul 14 2013 hwC0D3 crw-rw----+ 1 root audio 116, 4 Jul 14 11:31 pcmC0D0c crw-rw----+ 1 root audio 116, 3 Jul 14 11:31 pcmC0D0p crw-rw----+ 1 root audio 116, 2 Jul 14 2013 pcmC0D3p crw-rw----+ 1 root audio 116, 9 Jul 14 11:31 pcmC1D0c crw-rw----+ 1 root audio 116, 8 Jul 14 11:31 pcmC1D0p crw-rw----+ 1 root audio 116, 1 Jul 14 2013 seq crw-rw----+ 1 root audio 116, 33 Jul 14 2013 timer id uid=1338(neteler) gid=500(gis) groups=500(gis),499(vboxusers) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 Output of alsa-info --stdout ... attached to this report. Using pavucontrol I see that something comes in from the microphone (bar indicator) which I cannot hear, though. "Conclusion": It seems that alsa 1.0.25 is working while 1.0.26 fails with with type of USB headset. I am willing to assist with debugging if you tell me how to do that.
Created attachment 773268 [details] Output of alsa-info
Created attachment 773269 [details] Output of lsusb -v
you have to post the pulseaudio verbose log and pactl list http://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems it is strange that dB Max is less than 0dB USB Mixer: usb_id=0x05e12010, ctrlif=0, ctlerr=0 Card: USB VoIP Device at usb-0000:00:14.0-1, full speed Unit: 9 Control: name="PCM Playback Volume", index=0 Info: id=9, control=2, cmask=0x3, channels=2, type="S16" Volume: min=-8192, max=-64, dBmin=-3200, dBmax=-25
Created attachment 814912 [details] pulseaudio verbose log
Created attachment 814914 [details] pactl list
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hi there. I noticed the same behaviour with Fedora 21 (will probably update soon), so reopening. Is there anything new or something I can provide to help with investigation about this issue?
(In reply to Jakub Jelen from comment #9) > Hi there. I noticed the same behaviour with Fedora 21 (will probably update > soon), so reopening. I don't have the headset anymore (broken cable) so I couldn't re-test, and so the bug rot and rot ... > Is there anything new or something I can provide to > help with investigation about this issue? probably posting new logs could be useful, although it seems no one looked at them since #c6 ... but please do upgrade at first, F21 is really dead or try to install RHEL7 instead of upgrading Fedora, then clone the bug to draw some attention :-)
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.