[pulseaudio-discuss] F10 - change runlevel no audio no sound

[Colin Guthrie]

'Twas brillig, and zeek at 28/01/09 17:53 did gyre and gimble:
> Greetings,
> 
> Fedora 10 + sound = how much time do you have?
> 
> I have enough details on this to make your head spin. I've invested at 
> least six solid hours on this issue now. It began with the notorious
> 
> "How to: Fix PulseAudio and primary audio issues with Fedora 10"
> 
> http://forums.fedoraforum.org/showthread.php?t=206868
> 
> 
> --which solved the nasty audio issue. HOWEVER, I've now arrived at a 
> problem I will simply describe as (/etc/inittab):
> 
> 
> id:5:initdefault:	# AUDIO WORKS
> 
> id:3:initdefault:	# AUDIO DOES NOT WORK
> 
> 
> At runlevel 3 I simply do 'pulseaudio -k; pulseaudio -D' and this is 
> reported in /var/log/messages:
> 
> 
> Jan 28 12:30:43 mogwai pulseaudio[2073]: alsa-util.c: Error opening PCM 
> device hw:0: Permission denied
> Jan 28 12:30:43 mogwai pulseaudio[2073]: module.c: Failed to load 
> module "module-alsa-sink" (argument: "device_id=0 
> sink_name=alsa_output.pci_1039_7012_sound_card_0_alsa_playback_0 
> tsched=0"): initialization failed.
> Jan 28 12:30:43 mogwai pulseaudio[2073]: alsa-util.c: Error opening PCM 
> device hw:0: Permission denied
> Jan 28 12:30:43 mogwai pulseaudio[2073]: module.c: Failed to load 
> module "module-alsa-source" (argument: "device_id=0 
> source_name=alsa_input.pci_1039_7012_sound_card_0_alsa_capture_0 
> tsched=0"): initialization failed.
> 
> 
> 
> In runlevel 5 I get audio --but I want runlevel 3 for reasons I won't 
> get into here. In runlevel 5 I also get tons of these in the log...
> 
> 
> Jan 28 12:31:05 mogwai pulseaudio[2073]: module-alsa-sink.c: ALSA woke 
> us up to write new data to the device, but there was actually nothing to 
> write! Most likely this is an ALSA driver bug. Please report this issue 
> to the PulseAudio developers.
> Jan 28 12:31:05 mogwai pulseaudio[2073]: module-alsa-sink.c: ALSA woke 
> us up to write new data to the device, but there was actually nothing to 
> write! Most likely this is an ALSA driver bug. Please report this issue 
> to the PulseAudio developers.

Compare the output of ck-list-sessions at your two levels.

I suspect that your user is not getting permisson to open /dev/snd/* at 
runlevel 3. This is actually nothing to do with pulse but to do with how 
ConsoleKit assigns permissions to your user. Normally it works by adding 
an ACL to the device nodes in /dev/snd/* which you can check by running 
"getfacl /dev/snd/*"

Anyways, like I say it's not a pulse problem as this will affect playing 
sounds via alsa too.

That said I hope this points you in the right direction :p

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]