On 2023-01-27 09:52, Andrei Borzenkov wrote:
On Fri, Jan 27, 2023 at 11:24 AM Per Jessen <per@jessen.ch> wrote:
Overall, I don't subscribe to such band-aid "solutions", especially not when it ought to be easy to diagnose the problem. (sound is hardly black magic any more).
It most certainly is for anyone who does not spend their lifetime maintaining Linux sound stack. Even a simple task such as choosing an output device could be really daunting (I was immensely surprised when I plugged in headphones and lo and behold - I got a popup asking whether I have headphones, microphones or both. Without this question I would not even know where to start).
And it is not really limited to Linux. As soon as you have any issue in Windows the only recommendation you get is reinstalling drivers or management programs.
So yes, starting YaST is probably the most simple practical workaround. While I have seen many requests for some output related to sound problems on this list, I do not remember any actual solution based on the provided output (and I have a feeling that requesters did not really know what to do with it anyway). I do not count blanket "remove pulse and install pipewire" as "solution".
Thanks. You nailed it. So, my question is, if yast sound will go missing in the future (thinking of Leap, me), can someone find out what magic yast does so that we can replicate in the command line? I do not want a solution for my sound. I wanted it this summer, now it is magically working again (as has been working for many years, it is an old machine, after all) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)