Description of problem: Lack of volume on USB headset. Regression since F12. Version-Release number of selected component (if applicable): Rawhide How reproducible: Always Steps to Reproduce: 1. Connect headset 2. Turn up volume 3. Actual results: Almost inaudible until I restart pulseaudio. Still too low after restarting pulseaudio. In F12 the max volume is higher than what I have been able to get from rawhide, and I don't need to restart pulseaudio to get it. Sadly, even the max volume with F12 is low. In sound preferences I can drag the volume bar past 100%, but at the top it's still not at the volume I get as 100% in F12. Expected results: Music, loud music Additional info: The volume buttons on the headset work, but the mute button doesn't. The '+' button cannot turn the volume higher than 100% on the volume slider in sound preferences. dmesg doesn't seem to say anything interesting. Do you need pulseaudio -vvvv traces? Anything else?
Sounds like an issue with incorrect dB information provided by the card or the driver. Please check if "alsactl init 0" fixes your problem. If it doesn't, please run "alsamixer -c0" and try to find the mixer element that fixes your issue! If you find it, please provide the output of "amixer -c0" and tell us which element exactly you needed to change.
This USB headset becomes a new soundcard. tried alsactl init on both 0 and 1 with no effect What I had to do to get proper volume was to 'alsamixer -c1' and crank up 'Speaker'. I'll append amixer output for both card 0 and 1. The mute button on the headset doesn't work. Where does that belong? Is it some kind of HAL issue? Or is it a pulseaudio issue? Volume up/down buttons work. By the way... It would be very nice to have a possibility to set default output device directly from right-click on the gnome volume icon instead of having to open the 'Sound Preferences' to do it.
Created attachment 387992 [details] amixer -c0 output
Created attachment 387993 [details] amixer -c1 output
Regarding the g-v-c applet request, please open a seperate bug asking for this on gnome bz against gnome-media. If you use g-v-c do you have a drop-down on the output tab that allows you to choose "speaker" as output or something suchlike?
In the output tab I have a Balance slider and a 'Connector' dropdown with 'Analog Speaker' chosen as default. The other alternative is 'Analog Output'. The info for the headset in the Gnome Sound Preferences: - 'Hardware' tab: Logitech USB Headset 1 Output/1 Input Analog Stereo Output + Analog Mono Input - 'Output' tab: Logitech USB Headset Analog Stereo Stereo
I forgot to mention: The rawhide system had to be reused, so all the alsa info here is from F12 where the headset worked from the start, but with too little volume. I don't have a rawhide system available for testing at the moment.
So you are suggesting that the "speaker" element in "alsamixer -c1" is left untouched by g-v-c's volume slider, but it should be? Hmm, please provide the output of "pacmd ls"!
if I run alsamixer -c 1 and then use the gnome volume slider the volume in my earphones varies, but the slider in alsamixer stays still. Is this normal? As stated earlier, max volume is way too low. If I adjust the speaker slider in the alsamixer window from 0 to somewhere in the 80's (just entering red level) I get decent volume. (Speaker: dB gain about 2.45 or above) If I turn the gnome/pa volume all the way down alsamixer shows the muted state. This also happens if I use the volume buttons on the headset. The volume buttons on the headset affect the gnome volume slider. The mute button on the headset has no effect on anything.
Created attachment 390517 [details] pacmd ls output
The output clearly shows that you have a "speaker" output connector you can select in g-v-c's output tab. Please do so. Things will ten work for you.
There is "Analog output" and "Analog speaker". Which one I select has no effect. Both ajust the volume of the headset, and none of them provide full volume unless I use alsamixer also.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can confirm that this problem still occurs in F13. In order to get what I would consider a normal volume level with this headset, I have to go to PulseAudio Manager > Devices > Sinks > alsa_output.usb-Logitech_Logitech_USB_Headset-00.analog-stereo > Properties and crank the volume slider up to 480% (which is the upper limit).
What additional information is needed to get this fixed? I'd be happy to provide it.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.