<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><div>Quoting Rick Moen <rick@linuxmafia.com></div><div><br></div><div>> Yes, be _very_ careful about following online advice that used to apply,</div><div>> but may now be useless or actively harmful. </div><div><br></div><div>Exactly. That is why I stopped and asked for advice.</div><div><br></div><div>On some other occasions, I have found old complicated advice about how to do something, but newer releases had greatly simplified things. All I needed was to know what command to use.</div><div><br></div><div>Quoting Steve Litt (slitt@troubleshooters.com):</div><div><br></div><div>> I call Pulseaudio the land of a thousand mutes.</div><div><br></div><div>> I haven't used Ubuntu for a decade, but on most distros you can get rid</div><div>> of Pulseaudio, install ALSA, and use alsamixer to control device</div><div>> volumes.</div><div><br></div><div>Meanwhile, I have been consulting with a ham friend who had similar issues. She is using Debian. Her advise was to remove pulse and use alsamixer.</div><div><br></div><div>The only functionality is to output audio on the connector usually used for headphones. A volume control on the computer side is a plus, but not necessary.</div><div><br></div><div>BTW, I had a similar problem with Windoz. A rather obscure control panel had output set to 0. </div></div><br></div></div></body></html>