On the other hand, on this machine [Laptop – the other is a Desktop] – openSUSE 13.2 (Harlequin) (x86_64); AMD A10-5750M APU with Radeon™ HD Graphics; Richland [Radeon HD 8650G] – there was no issue raised with respect to KMix following today’s 2015-11-20 update:{ Both are AMD CPU/Motherboard/Graphic devices machines . . . }
I don’t know if this would be of any use to you, but I eventually realized that the reason YaST had sound was that I was super user. Once I realized that only root had normal audio, I found a number of posts from people suggesting that I remove Pulse Audio. I did, and it fixed my sound.
Maybe adding your user to the audio group may have worked. Also since root worked did you try a different normal user. the config files in your home can get messed up sometime.
The sound device is owned by user root and group audio, that hasn’t changed. A different user has to be part of the group audio to have access.
And in openSUSE PulseAudio is started by/for the user, so the user does need to have access to the sound card or PulseAudio won’t work either.
Nowadays, a user that is logged in locally will get granted access automatically by systemd’s logind (via ACLs).
But the current problem with polkit could prevent this.
The other two groups are probably only relevant if PulseAudio is running as system-wide daemon, which it is not by default in openSUSE.
But just to be clear: you need to logout and login (or reboot) after adding your user to some group for the change to take effect.
Another thing that might help: delete the folder ~/.config/pulse/ to reset pulseaudio’s user settings.
I had this exact same problem after I updated today (21st of November 2015) using yast. None of the KDE notification sounds worked thereafter. Yast had insisted on a repo change for gstreamer and related packages from openSUSE to packman to meet dependencies. So, I reverted to an rsync backup that I had just previously made and I did the same update again with zypper instead of yast which did not complain about any dependencies. After doing the update with zypper, sound is working fine. However, if I now do a software update with yast then it insists on this same repo change for gstreamer and related packages whereas zypper says “Nothing to do.”. FWIW, Apper does not try to do the repo change either. So, something strange is going on with yast while the software update goes just fine with zypper. In my case, sound quite working because yast insisted on switching repos from openSUSE to packman for gstreamer and related packages. I don’t know if this helps or why yast has become confused but I bet that may be the source of your problem too.
You may want to check the repo that gstreamer and related packages is using and, if they are using packman, then use zypper to set the repo back to openSUSE instead of packman since that is the only difference in my install that made sound stop working after this update.
Having read the previous posts, I began to realise that I had also enabled the systemdTimidity service – stopped and disabled timidity.service – et voilà! :shame:
Internal Analogue Stereo
reappeared – no logout/login required; - disabled the Cape Verde/Pitcairn HDMI Audio
; - pushed the Internal Analogue Stereo
back to number 1 in the KMix audio device list.
Need to check if the other users also have sound again.
Yeah, right. I totally forgot about this again.
That’s actually one of the reasons why I don’t use PulseAudio…
If timidity is running as system service, it blocks PulseAudio (started as user) to gain exclusive access to the sound card, thus breaking audio if PulseAudio is enabled.
So, if you want to use timidity (as system-wide daemon), you need to disable PulseAudio.
It is also possible to run timidity as user, in combination with PulseAudio though. See /usr/share/doc/packages/timidity/README.SUSE for how to do that.
That “problem” exists since years though, not just since recent updates…
Answering your question in my thread in this thread…
I never had timidity loading or any MIDI software AFAIK. I did change my sound server from ESOUND to Audio Pulse and then back, but I spent (read wasted) most of my time trying to reconfigure client software.
