I’m running Tumbleweed and sound which previously worked has stopped working. in pavucontrol, both sound cards are listed with the profile set to off. When I try and select a profile, all of them are listed as unavailable. KDE audio control lists the profile as off. My user is a member of both the audio and pulse groups.
When I added the user to the pulse and audio groups, I only logged out and back in. The profiles were still unavailable. However, after rebooting the profiles became available. Not sure why the difference, but the issue is resolved.
Great it works, and consider this a contribution to openSUSE. Others have reported this kind of issues, on other platforms. Will ask around if pulse and/or audio group addition to the user privs helps their issues.
I wrote too soon. I applied an update yesterday and rebooted. Now I’m back to the state where the profiles are listed as unavailable. The user is a member of the audio and pulse groups and the files under /dev/snd appear to have the proper permissions.
It does not change the behavior. After running “pulseaudio -k” I get a brief pop up saying dummy output and the actual profiles remain unavailable in the pavucontrol.
Allow it to upload the output to an online server, and post the link to this here.
BTW, this will show what parameters are in effect with respect to the loaded ‘snd_hda_intel’ module.
systool -m snd_hda_intel -v
If this all checks out, it could be an issue with udev/PulseAudio itself. I’ve seen a few such bug reports online, but I haven’t seen such reports from the openSUSE community.
Save when done and then reboot. The sound card order should now have the ‘Realtek ALC898’ as the first device. I don’t know whether this would make any difference to PulseAudio, but I did wonder if the NVIDIA device was somehow causing PA to fail.
I did a clean install of Tumbleweed and added my user to the pulse, pulse-access, and audio groups, but the problem persisted. I had an extra space on after the user name in /etc/groups for the pulse group. After removing that and restarting to make sure the user was a member of the audio group, it still persisted. Then I ran pulseaudio -k and the problem no longer occurs. Not at all clear to me we why restarting pulseaudio worked that time and not before. The problem is no resolved for me.