Bug 713554

Summary:	Tumbleweed: rcalsasound + systemd -> does nothing
Product:	[openSUSE] openSUSE 11.4	Reporter:	Jon Nelson <jnelson-suse>
Component:	Sound	Assignee:	Takashi Iwai <tiwai>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fcrozat
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jon Nelson 2011-08-22 21:40:54 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0

With systemd is in use, "rcalsasound restart" does nothing. 
:-(




Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Jon Nelson 2011-08-22 21:49:50 UTC

But "bash -x /usr/sbin/rcalsasound" does.
Weird.

Comment 2 Frederic Crozat 2011-09-08 12:44:46 UTC

does systemctl restart alsasound work ?

Comment 3 Jon Nelson 2011-09-10 15:50:54 UTC

No. It grumps about some module or the other not found.
I should note that I don't get *any* sound when I boot with systemd.

Comment 4 Jon Nelson 2011-09-10 15:54:02 UTC

worklaptop:~ # systemctl restart alsasound
Failed to issue method call: Unit name alsasound is not valid.
worklaptop:~ # systemctl  | grep alsa
worklaptop:~ #

Comment 5 Jon Nelson 2011-09-10 16:00:36 UTC

It's not that "rcalsasound" does nothing (even w/systemd), actually that seems to work OK (I can verify that modules are loaded/unloaded, etc...).

It's pulseaudio. It can't "find" the sound cards.  /proc/asound/cards shows stuff, but pulseaudio shows only "Dummy Output".

Comment 6 Jon Nelson 2011-09-10 16:16:45 UTC

More info - I cranked up pulseaudio's log level.

pulseaudio *when started under systemd* claims to be unable to access /dev/snd/control* devices (strace shows this to be true).  I added myself to the 'audio' group, logged out, logged in, *had to kill pulseaudio because it didn't exit with my session*, and *then* I had sound again:


Sep 10 11:08:47 worklaptop pulseaudio[4197]: module-udev-detect.c: /dev/snd/controlC0 is accessible: no
Sep 10 11:08:47 worklaptop pulseaudio[4197]: module-udev-detect.c: /dev/snd/controlC29 is accessible: no


after:

Sep 10 11:13:43 worklaptop pulseaudio[5771]: module-udev-detect.c: /dev/snd/controlC1 is accessible: yes
Sep 10 11:13:48 worklaptop pulseaudio[5771]: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes
Sep 10 11:13:48 worklaptop pulseaudio[5771]: module-udev-detect.c: /dev/snd/controlC1 is accessible: yes

Comment 7 Jon Nelson 2011-09-10 20:55:47 UTC

Found the same problem description here:

https://bbs.archlinux.org/viewtopic.php?pid=969950#p969950

Comment 8 Frederic Crozat 2011-09-11 09:48:30 UTC

to restart a service :

systemctl restart alsasound.service

Comment 9 Takashi Iwai 2011-09-26 08:19:56 UTC

It was a known problem of systemd with udev.

Anyway, systemd was dropped from Tumbleweed now, so no need to track any longer.  Let's close.