[Bug 26483] Ubuntu5.10 not configured for Alsa device:surround51; Alsa-esd incompatibilities.

[Manuel Iglesias Alonso]

Public bug report changed:
https://launchpad.net/malone/bugs/26483

Comment:
Did you read my last comments Sebastien?

I am using the default Ubuntu set-up with linux-image2.6.12-10-686-smp,
version 2.6.12-10.26 and alsa-base 1.0.9b-4.


I want to use several applications with Alsa driver 'surround51' (6 channels: FrontLeft, FrontRight, Centre, RearLeft, RearRight and Woofer). Applications: aplay, xmms, xine and mplayer.


If Ubuntu and Alsa were properly matched I would expect correct operation of all applications. Unfortunately I find the following problems:

All the applications (aplay, xmms, xine and mplayer), using Alsa device
'surround51', while playing, cause Alsa to output continuously: 'ALSA
lib pcm_dmix.c:802:(snd_pcm_dmix_open) unable to open slave' to $HOME
/.xsession-errors (Details in previous comment).

Some applications using Alsa device 'surround51' launched from
GnomePanel either give an error message or do not start to reproduce
sound for about 7 seconds: 'xmms' and 'xine' give error messages;
'aplay -Dsurround51 File.wav' does not start for about 7 seconds
(Details in previous comment). 'xmms' and 'aplay -Dsurround51 File.wav'
start all right if 'esd' is not running (stopped by 'killall esd').

Note: All the applications (aplay, xmms, xine and mplayer) start all
right and do not cause Alsa to output error messages to $HOME/.xsession-
errors if they are configured for Alsa device 'default'.


Hope I have made myself clear this time. Please run 'aplay -Dsurround51 File.wav' (A big file) launched from GnomePanel (Steps described in previous comment) in an Ubuntu system and check 7 seconds delay in starting and error messages in $HOME/.xsession-errors.


Best regards,
Manolo.