Red Hat Bugzilla – Bug 502299
KMix doesn't unmute correctly
Last modified: 2009-12-30 13:34:31 EST
Created attachment 345188 [details]
Output of alsa-info.sh --no-upload
Description of problem:
If sound is muted at boot kmix doesn't unmute it.
I must use alsamixer, press 'm' twice to mute/unmute and kmix is again able to handle mute/unmute correctly.
Version-Release number of selected component (if applicable):
$ kmix -v
KDE: 4.2.3 (KDE 4.2.3)
Steps to Reproduce:
1. Mute sound using kmix
3. Unmute sound using kmix
3. Play something => no sound
4. Run alsamixer and press 'm' twice to mute/unmute
5. Play something => sound and kmix can mute/unmute
Kmix is not able to unmute sound if it was muted in a previous session, even though osd notifications appear correctly.
Kmix should be able to unmute sound without requiring manual unmuting using alsamixer.
Created attachment 345189 [details]
Output of amixer -c0 when sound doesn't work
Created attachment 345190 [details]
Output of amixer -c0 when sound works
Except for volume thresholds it doesn't seem to be anything different from amixer_c0_nosound
I cannot reproduce, as I leave my sound muted almost all the time (esp on login), and unmuting works fine... *most* of the time.
The few times it hasn't it was PulseAudio doing funky things. These cases of PA wierdness were usually after a suspect/resume. I either had to run pavucontrol and mute/unmute things all over, to get it to work again, or pavucontrol would simply report my output device as "Null" (logout/login and/or killing and auto restarting PA helped me).
Any of that sound familiar?
Sadly, no. This doesn't happen after a suspend/resume but after a simple reboot.
By the way, I have just installed pavucontrol and muting/unmuting made it work again (same behaviour as alsamixer though).
The fact that this happens only if sound was muted in the previous session makes me wonder if something weird gets stored somewhere. (If so, the next question would be: what and where?)
Please report this issue upstream at http://bugs.kde.org and also please add
the upstream information to this report. We will monitor upstream for a
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
I have similar situation on Fedora 12 every KDE 4.x versions.
Sometimes sound is muted after restart and can't be unmuted with kmix
I must use gnome-volume-control to unmute it.
But it must have something in common with gnome, because
when gnome-volume-control is running kmix can mute the sound only
unmute doesn't work
How to reproduce:
1. Open Gnome sound preferences gnome-volume-control
2. Mute sound using kmix
3. Unmute sound using kmix
kmix shows that sound is unmuted but gnome-volume-control show it's muted
4. Play something => no sound
I'd venture PA flat volumes may have something to do with it.
When these problem occur, please use pavucontrol to double-check PA volumes.
Seem's OK with pavucontrol.
I took my camera and shoot 2 short problem presentations
(files can be downloaded 10 times only)