Carlos E. R. wrote:
On 2022-06-24 10:56, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-06-24 10:10, Per Jessen wrote:
I can't help but suspect some configuration conflict/issue - that you need to fiddle with yast whereas I don't, that is odd. Given that my config works without a yast sound config, in your situation I would be tempted to get rid of it and start from there.
And do what? I don't know how to activate sound except by using YaST, since decades.
and I don't recall having had to do that, for years. I don't know what the yast sound config does, but on my desktop systems (also quite old), it doesn't seem to be required. My suspicion is that the yast config is _somehow_ getting in the way on your system. Starting with a clean slate might help with the diagnosis.
On other machines, I don't have to do anything, it works directly from installation. Not in this. Anyway, I do not know how to "start with a clean slate". Install openSUSE again? Not doable, machine is in production, several people use it. And I am too busy to do that, they would behead me for wasting time on the computer :-p
Just clean as far as the sound config goes. Simply get rid of the pulseaudio stuff configured by yast.
What I have done, is insert this code in one of my boot scripts:
/usr/bin/logger -t Mine -p daemon.info \ "Reseting sound system with yast." yast sound remove && yast2 sound add
And that solves the issue.
It all depends on what you want - a kludgy work around as the above or actually solve the problem ;-) Me, I don't like work arounds for what appears to be a pretty banal problem. -- Per Jessen, Zürich (22.6°C) Слава Україні! Slava Ukraini!