The properties: application.name and, among others, should help here. With the offending application playing audio, run:įind and make note of the index of the corresponding sink input. If a specific application is muted or low while all else seems to be in order, it may be due to individual sink-input settings. This will cause amixer to ask PulseAudio to do the toggling rather than toggling it directly.īecause of this, PulseAudio will correctly unmute Master as well as any applicable output. To resolve this, amixer must have the device flag set to 'pulse': 'Headphone' and 'Speaker'), using plain amixer to toggle Master can trigger PulseAudio to mute the active output too, but it does not necessarily unmute it when Master is toggled back to be unmuted. Output stuck muted while Master is toggled If it displays a low percentage value, you can run pamixer -i 10 several times to turn up the volume gradually. If the output says muted, run pamixer -u to unmute. To troubleshoot via CLI only, install pamixer and check the output of the following command: Install pavucontrol and check if there is any output on the pavucontrol panel when playing a. One possible cause of no sound after install is that PulseAudio detects the wrong output device as a default. Note: alsamixer will not tell you which output device is set as the default.
