ESOUND works alternatively in UBUNTU 7.10 and Dell Inspiron 1520

Hello

i don't know when it started, but i recorded it from 1.18.5.3 and this problem still exist on 1_19_1_3_RELEASECANDIDATE:

At first start, Second Life don't recognize esound system on a Ubuntu 7.10

2008-03-27T17:28:38Z INFO: init: Trying ESD audio output...
2008-03-27T17:28:38Z WARNING: ESD audio output FAILED to initialize: Error initializing output device.

Then, closing and re opening the viewer it works:

2008-03-27T17:31:57Z INFO: LLAudioEngine_FMOD::init() initializing FMOD
2008-03-27T17:31:57Z INFO: init: Trying ESD audio output...
2008-03-27T17:31:57Z INFO: ESD audio output initialized OKAY
2008-03-27T17:31:57Z INFO: init: Audio output: ESD
2008-03-27T17:31:57Z INFO: LLAudioEngine_FMOD::init() FMOD initialized correctly
2008-03-27T17:31:57Z INFO: setStartupState: Startup state changing from 0 to 1
2008-03-27T17:31:57Z INFO: idle_startup: Initializing Multimedia....

Then, closing and re opening viewer:

2008-03-27T17:32:48Z INFO: LLAudioEngine_FMOD::init() initializing FMOD
2008-03-27T17:32:48Z INFO: init: Trying ESD audio output...
2008-03-27T17:32:48Z WARNING: ESD audio output FAILED to initialize: Error initializing output device.

And so on.

I'm on a Dell Inspiron 1520 so lspci show:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

Bye

Try to start the esound daemon as root in the init scripts while booting.

I had similar problems using the automatic esd-start as user.

let me guess: you find 1 socket for esd in /tmp before the first start (for example) :
/tmp/.esd-0/socket

and 2 sockets after the first start (example):

/tmp/.esd-0/socket
/tmp/.esd-1000/socket

(more general: /tmp/.esd-<userid>/socket)

after the second start. The examples would mean that you start esd in the init as root, so the access as normal user is not allowed, fmod fails to access and starts a second esd socket for your user, which then is open for access at the second start.
I had this, too, and for me the solution was not to start esd in the init but only from the autostart-folder of my secondlife user with "esd &" as command.

starting esound daemon as root in startup script made SL crash badly.

But thanks Armin Weatherwax suggestion i discovered what is happening.

10. At startup on /tmp directory there's no esd sock.
Starting SL first time it don't work

2008-03-29T12:50:06Z INFO: init: Trying ESD audio output...
2008-03-29T12:50:07Z WARNING: ESD audio output FAILED to initialize: Error initializing output device.

but the socket appear on /tmp:

drwxrwxrwt 2 patadx patadx 4096 2008-03-29 13:50 .esd

Then, closing SL the socket still is in /tmp dir and starting SL again it work:

2008-03-29T12:52:38Z INFO: init: Trying ESD audio output...
2008-03-29T12:52:38Z INFO: ESD audio output initialized OKAY
2008-03-29T12:52:38Z INFO: init: Audio output: ESD

BUT closing SL with audio working ESD socked disappear and then, starting it againt, it don't work (do you remember commodore64? then goto 10 )

A question for Armin. What's the Autostart folder you're talking on previous post? If i start esd in another shell it work correctly.

Thanks in advance

lol - i expected that question the moment after i pressed submit: for i am using kubuntu i have a ~/.kde/autostart/ , which - surprise - can be used to start whatever liked with the kde session. I don't know the gnome way for doing so - but using the terminal does it anyway

Thank you Armin,

i solved.

Bye