[pulseaudio-discuss] main.c: daemon startup failed.

[Sean McNamara]

On Mon, 2008-04-14 at 09:15 +1000, Ben Finney wrote:
> Sean McNamara <smcnam at gmail.com> writes:
> 
> > On Sun, 2008-04-13 at 18:34 +1000, Ben Finney wrote:
> > 
> > > What can I do next to diagnose this further?
> > 
> > 1. Start the daemon with -vvvv --daemonize=false, and try running it
> > alternately as root and non-root. Paste the full console output to
> > us.
> 
> $ /usr/bin/pulseaudio -vvvv --daemonize=false
> E: main.c: Root priviliges required.
> 
> 
> $ sudo /usr/bin/pulseaudio -vvvv --daemonize=false
> [sudo] password for bignose:
> I: main.c: Found user 'pulse' (UID 112) and group 'pulse' (GID 113).
> I: main.c: Successfully dropped root privileges.
> W: pid.c: Stale PID file, overwriting.
> W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
> W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
> I: main.c: Page size is 4096 bytes
> I: main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
The above line is pretty good advice. No hrtimers means you're likely to
get dropouts. Very likely. Even if you resolve the problems keeping
sound from nominally working, it will probably not be enjoyable for you,
particularly when the system is under moderate CPU or cache load. But,
the prior problem of getting sound at all still remains... What version
of ALSA are you running?
> D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules//module-hal-detect.so': success
> I: module-hal-detect.c: Trying capability alsa
> D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_timer
> D: module-hal-detect.c: Loading module-alsa-sink with arguments 'device_id=0 sink_name=alsa_output.pci_106b_3e_alsa_playback_0'
> D: alsa-util.c: Trying front:0...
> I: module-alsa-sink.c: Successfully opened device front:0.
> I: module-alsa-sink.c: Successfully enabled mmap() mode.
> ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
> I: alsa-util.c: Unable to attach to mixer front:0: No such file or directory
> I: alsa-util.c: Successfully attached to mixer 'hw:0'
> I: alsa-util.c: Cannot find mixer control "Master".
> I: alsa-util.c: Using mixer control "PCM".
> I: sink.c: Created sink 0 "alsa_output.pci_106b_3e_alsa_playback_0" with sample spec "s16be 2ch 44100Hz"
> I: source.c: Created source 0 "alsa_output.pci_106b_3e_alsa_playback_0.monitor" with sample spec "s16be 2ch 44100Hz"
> I: module-alsa-sink.c: Using 4 fragments of size 4408 bytes.
> I: alsa-util.c: All 2 channels can be mapped to mixer channels. Using hardware volume control.
> D: module-alsa-sink.c: Thread starting up
> D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
> I: module-alsa-sink.c: Starting playback.
> I: module.c: Loaded "module-alsa-sink" (index: #0; argument: "device_id=0 sink_name=alsa_output.pci_106b_3e_alsa_playback_0").
It looks like the sink correctly opened, but...
> D: module-hal-detect.c: Loading module-alsa-source with arguments 'device_id=0 source_name=alsa_input.pci_106b_3e_alsa_capture_0'
> D: alsa-util.c: Trying front:0...
> I: alsa-util.c: Couldn't open PCM device front:0: No such device
> D: alsa-util.c: Trying surround40:0...
> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0
> ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM surround40:0
> I: alsa-util.c: Couldn't open PCM device surround40:0: Invalid argument
> D: alsa-util.c: Trying surround41:0...
> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0
> ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM surround41:0
> I: alsa-util.c: Couldn't open PCM device surround41:0: Invalid argument
> D: alsa-util.c: Trying surround50:0...
> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0
> ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM surround50:0
> I: alsa-util.c: Couldn't open PCM device surround50:0: Invalid argument
> D: alsa-util.c: Trying surround51:0...
> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0
> ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM surround51:0
> I: alsa-util.c: Couldn't open PCM device surround51:0: Invalid argument
> D: alsa-util.c: Trying surround71:0...
> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0
> ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM surround71:0
> I: alsa-util.c: Couldn't open PCM device surround71:0: Invalid argument
> D: alsa-util.c: Trying hw:0 as last resort...
> E: alsa-util.c: Error opening PCM device hw:0: No such device
> E: module.c: Failed to load  module "module-alsa-source" (argument: "device_id=0 source_name=alsa_input.pci_106b_3e_alsa_capture_0"): initialization failed.
The source didn't open. The "E" indicates this is an unrecoverable
error, IIRC... in other words, this is causing PA to exit.
Can you use the "arecord" program on hw:0? Is there any reason for you
to suspect that your hardware doesn't support sound input? You haven't
stated what chipset you're using yet, unless I've just missed it...
> D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_106b_3e_alsa_capture_0
> D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_106b_3e_alsa_control__1
> I: module-hal-detect.c: Loaded 1 modules.
> I: module.c: Loaded "module-hal-detect" (index: #1; argument: "").
> I: module.c: Loaded "module-esound-protocol-unix" (index: #2; argument: "socket="/tmp/.esd/socket"").
> I: protocol-native.c: Allowing access to group 'pulse-access'.
> I: protocol-native.c: loading cookie from disk.
> I: module.c: Loaded "module-native-protocol-unix" (index: #3; argument: "").
> I: module.c: Loaded "module-esound-protocol-tcp" (index: #4; argument: "").
> I: protocol-native.c: Allowing access to group 'pulse-access'.
> I: protocol-native.c: using already loaded auth cookie.
> I: protocol-native.c: Allowing access to group 'pulse-access'.
> I: protocol-native.c: using already loaded auth cookie.
> I: module.c: Loaded "module-native-protocol-tcp" (index: #5; argument: "").
> D: module-zeroconf-publish.c: Publishing services in Zeroconf
> D: module-zeroconf-publish.c: Successfully created entry group for pulse at lily: ALSA PCM on front:0 () via DMA.
> I: module.c: Loaded "module-zeroconf-publish" (index: #6; argument: "").
> I: module-volume-restore.c: starting with empty ruleset.
> I: module.c: Loaded "module-volume-restore" (index: #7; argument: "").
> I: module.c: Loaded "module-default-device-restore" (index: #8; argument: "").
> I: module.c: Loaded "module-rescue-streams" (index: #9; argument: "").
> D: module-suspend-on-idle.c: Sink alsa_output.pci_106b_3e_alsa_playback_0 becomes idle.
> D: module-suspend-on-idle.c: Source alsa_output.pci_106b_3e_alsa_playback_0.monitor becomes idle.
> I: module.c: Loaded "module-suspend-on-idle" (index: #10; argument: "").
> D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules//module-x11-publish.so': success
> D: module-x11-publish.c: using already loaded auth cookie.
> X connection to localhost:10.0 broken (explicit kill or server shutdown).
You should probably comment out module-x11-publish
from /etc/pulse/default.pa. It's not as useful as it sounds, and
depending on the circumstances, that X error alone could be causing the
server to shut down.
> 
HTH,

-Sean