Sorry, miss this NI. I would not guess it's caused by the *pulse-rust* backend. It has been tested for a while since *FF 60* (bug 1440538). The comment 0 says *FF68* is fine so the problem should be on somewhere else. The cause may be something related to bug 1422637. (In reply to Alex Chronopoulos [:achronop] from comment #6) > In addition to the above can you please add the pavucontrol tool and check the volume of Firefox application in there. In general, have you made any change in PulseAudio setup? > > Finally, since the problem started after an upgrade, would be possible to run the mozregression tool and find the patch that broke it? Barnet, I was wondering if you could use [mozregression](https://mozilla.github.io/mozregression/) to help us to narrow down the range of the cause, and check if you made any changes in the *PulseAudio* settings.
Bug 1627325 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry, miss this NI. I would not guess it's caused by the *pulse-rust* backend. It has been tested for a while since *FF 60* (bug 1440538). The comment 0 says *FF68* is fine so the problem should be in somewhere else. The cause may be something related to bug 1422637. (In reply to Alex Chronopoulos [:achronop] from comment #6) > In addition to the above can you please add the pavucontrol tool and check the volume of Firefox application in there. In general, have you made any change in PulseAudio setup? > > Finally, since the problem started after an upgrade, would be possible to run the mozregression tool and find the patch that broke it? Barnet, I was wondering if you could use [mozregression](https://mozilla.github.io/mozregression/) to help us to narrow down the range of the cause, and check if you made any changes in the *PulseAudio* settings.