FS#36495 - Default permissions for sound devices not set correctly

Attached to Project: Arch Linux
Opened by Curtis (foxcm2000) - Monday, 12 August 2013, 00:55 GMT
Last edited by Dave Reisner (falconindy) - Monday, 12 August 2013, 12:30 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
  • Anonymous Submitter (2013-08-12)
Private No

Details

Description:
Recently programs that produce sound (including cmus and VLC to name a couple) failed after a reboot. I noticed that the /dev/snd/timer and /dev/snd/seq files had permissions as root-only. My user was originally in the 'audio' group so I did a manual chmod g+rw for those files and sound started working as expected. I have read the systemd article and it said that I should not put my user in the 'audio' group... so I removed my user from this group. Afterwards, as you might expect, audio completely stopped working again only this time I need to add global +rw permissions to all files in the /dev/snd directory to get audio working. How can I get a better solution for these permission issues?

Notes: I am not running pulse audio or any other sound server (and I don't want to). The sound card modules load fine at boot and outside of the permissions issue, audio works perfectly.
Hardware: Xonar DX (virtuoso driver).

Additional info:
* package version(s)

lsmod | grep snd output:
snd_virtuoso 30214 1
snd_oxygen_lib 27565 1 snd_virtuoso
snd_mpu401_uart 5323 1 snd_oxygen_lib
snd_rawmidi 17079 1 snd_mpu401_uart
snd_seq_device 4652 1 snd_rawmidi
snd_pcm 65724 2 snd_oxygen_lib
snd_page_alloc 6706 1 snd_pcm
snd_timer 17391 1 snd_pcm
snd 49104 8 snd_timer,snd_pcm,snd_rawmidi,snd_virtuoso,snd_oxygen_lib,snd_mpu401_uart,snd_seq_device


Contents of /dev/snd [before being fixed]:
drw-rw---- 2 root root 60 Aug 11 20:22 by-path
crw-rw---- 1 root audio 116, 0 Aug 11 20:22 controlC0
crw-rw---- 1 root audio 116, 24 Aug 11 20:22 pcmC0D0c
crw-rw---- 1 root audio 116, 16 Aug 11 20:37 pcmC0D0p
crw-rw---- 1 root audio 116, 25 Aug 11 20:22 pcmC0D1c
crw-rw---- 1 root audio 116, 17 Aug 11 20:22 pcmC0D1p
crw------- 1 root audio 116, 1 Aug 11 20:22 seq
crw------- 1 root audio 116, 33 Aug 11 20:22 timer

After kludgy chmod workaround:

ll /dev/snd/
total 0
drw-rw---- 2 root root 60 Aug 11 20:22 by-path
crw-rw-rw- 1 root audio 116, 0 Aug 11 20:22 controlC0
crw-rw-rw- 1 root audio 116, 24 Aug 11 20:22 pcmC0D0c
crw-rw-rw- 1 root audio 116, 16 Aug 11 20:37 pcmC0D0p
crw-rw-rw- 1 root audio 116, 25 Aug 11 20:22 pcmC0D1c
crw-rw-rw- 1 root audio 116, 17 Aug 11 20:22 pcmC0D1p
crw-rw-rw- 1 root audio 116, 1 Aug 11 20:22 seq
crw-rw-rw- 1 root audio 116, 33 Aug 11 20:22 timer
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 12 August 2013, 12:30 GMT
Reason for closing:  Works for me
Additional comments about closing:  More likely that this is the user's setup. Reopen if there's an actual bug for Arch to address.
Comment by Dave Reisner (falconindy) - Monday, 12 August 2013, 01:09 GMT
Looks like ACLs aren't being applied. You should figure out why logind isn't giving you an active session. Running the following *should* show Active=yes on a healthy system:

loginctl show-session ${XDG_SESSION_ID?Broken}

How do you login and start X? Are you using testing?

This sounds more like a support question than a bug report.........
Comment by Eric Belanger (Snowman) - Monday, 12 August 2013, 01:57 GMT
Dave: When I mentioned this issue on IRC, you told me it was a systemd bug, namely  FS#36259 .
Comment by Dave Reisner (falconindy) - Monday, 12 August 2013, 02:13 GMT
But that's a different issue than this "bug". OP in this case has no ACLs applied.  FS#36259  is about permissions on static nodes (such as /dev/snd/seq, /dev/loop, or anything else from modules.devname). Looking back through IRC logs, you explicitly asked about /dev/fuse, which is indeed a static node and covered by the bug in  FS#36259 .

But along that vein, OP hasn't mentioned whether they're using [testing] or not. I simply assumed they weren't since they were filing against [core].
Comment by Curtis (foxcm2000) - Monday, 12 August 2013, 11:54 GMT
Thanks for the lead about ACLs. I'll investigate further to figure out why they aren't being applied and let you know if it is a bug or just a weird config issue that I can get fixed myself.

Loading...