http://bugzilla.suse.com/show_bug.cgi?id=983939 http://bugzilla.suse.com/show_bug.cgi?id=983939#c1 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Ladislav Slezák --- Um, this does not look like a regression, I have Leap 42.1 and I'm not included in the "audio" group but I can play sound without any problem:

groups users vboxusers ll /dev/snd/controlC0 crw-rw----+ 1 root audio 116, 2 13. čen 08.32 /dev/snd/controlC0 getfacl /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 # owner: root # group: audio user::rw- user:lslezak:rw- group::rw- mask::rw- other::---

The standard unix permissions are for root:audio, but the ACLs specify extra permissions for me. IIRC these permissions are granted during the login process (ConsoleKit/PAM/or something else? I am not expert in that area...) - Check the file permissions (see the commands above) - Check whether your root FS supports ACLs and the support is not disabled (check /etc/fstab) If you really need to have the new uses in the "audio" group then start the YaST User management module and switch to "Defaults for New Users" tab, add "audio" to the "Secondary Groups" field. Resolving as INVALID, the audio group membership should not be needed, if it stopped working that something else outside YaST got broken, the YaST default groups should not be involved at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=983939 http://bugzilla.suse.com/show_bug.cgi?id=983939#c3 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #3 from Wolfgang Bauer --- Be aware that there was a problem with this in Tumbleweed recently: http://lists.opensuse.org/opensuse-factory/2016-06/msg00113.html Running "pam-config --add --systemd" manually should fix your system. The problem itself has been fixed in newer snapshots (by reverting pam-config), though just installing current updates will *not* change anything. A fresh installation should work too, though. -- You are receiving this mail because: You are on the CC list for the bug.