Created attachment 1076315 [details] pulseaudio logs Description of problem: Days ago I disabled PulseAudio's flat volumes due PulseAudio: - crackling audio trouble #1264177 - inability to correctly handle application bad behaviour about volume levels #1265267 Disabling PulseAudio's flat volumes solved the mentioned problems, but introduced a new one. I usually increase / decrease volume level by using mouse wheel on KMix icon. Both actions sometimes trigger the master volume to 100% level. While collecting PulseAudio logs, I managed to reproduce (twice) the problem: Note: each mousewheel step increases or decreases volume level by a 5%. ===First occurrence of the problem=== At line number 1359 you can see the volume setted at 70%: A few moments later, I tried to increase it at 75%, but the volume level has been pushed to 100% (line number 1459). ===Second occurrence of the problem=== At line number 18000 you can see the volume setted at 40%: A few moments later, I tried to increase it at 45%, but the volume level has been pushed to 100% (line number 18016). Since on the logs, every volume level change has the form of D: [alsa-sink-Multichannel] alsa-sink.c: Requested volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB that "Requested volume" makes me think about PulseAudio being requested to set the volume to 100%. So in the dubt I added in CC some guys of KDE SIG and alsa. I can quite easly reproduce the problem, so feel free to ask me to do any test. Version-Release number of selected component (if applicable): pulseaudio-6.0-8.fc22.x86_64 kmix-15.04.0-1.fc22.x86_64
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
There's already an upstream report, let's continue tracking it there.