Re: portaudio2/device busy?
On Sunday 25 January 2009 17:21, Tamas Hegedus wrote:
> Nigel Henry wrote:
> > I assume that you had installed pulseaudio at some time or other, to try
> > it
>
> Yes, I installed it myself. Since when I was fighting to set up my
> audio, at a point I red that I need a sound server. So I installed it
> and the sound was working on my linux box.
>
> > Installing the sysv-rc-conf package could help. run it as root on the
> > command line, and you can disable pulseaudio (for example), which saves
> > having to kill it, each time you boot up.
>
> After I killed pulseaudio:
> However, 'espeak' was working, I got the message that "can not connect
> to pulseaudio".
>
> So last night I thought I do not need pulseaudio, so I simply removed
> it. Rebooted.
> But now still everything complains that "can not connect to pulseaudio"
> and no sound at all.
>
> I tried to google and find a site where I can understand the sound
> architecture of Linux (not ALSA - but the whole picture), but I could
> not find anything.
>
> So I do not know now how to proceed. Can you suggest something to
> read/learn?
>
> And also something how to solve the situation:
> * having a soundserver (pulseaudio? or should I use esound?) for the
> common sound applications
> * having espeak to work - w/o a soundserver (wrapping around it to avoid
> the server layer)
>
> I have tried aoss - it was working for 'aoss flite -t "test sound"'
> (flite needs oss) but not for 'aoss espeak "test sound"'...
>
> Thanks again,
> tamas
Hi Tamas.
You should not need to use any sound servers, whether ESD, aRts (KDE), or
Pulseaudio, to just use audio apps. Most audio apps will use Alsa directly
without any sound server entering the equation. If you have audio apps that
are OSS based, you will need to install the package alsa-oss.
let's go back to Pulseaudio. On some distros it's installed as default, and
I've seen quite a few folks having problems with it. On Fedora, it's easy
enough to disable, by removing the package alsa-plugins-pulseaudio, then all
the audio apps use alsa directly. Debian based installs are different, and
that package does not exist. I've seen that the correct way is do the
following to get rid of pulseaudio from a debian install. I use apt, not
aptitude, so this is the apt-get command below.
apt-get remove pulseaudio --purge
Also open synaptic as root, and check to see if any pulseaudio stuff is still
installed. If there are any pulseaudio packages still installed, be carefull
about just going ahead and removing them, as some want to remove other
packages as deps, which may screw things up completely.
Also have a look in your home/user directory. You may find pulseaudio stuff
there. It's safe to just delete it. I only see one on my Ubuntu Intrepid 8.10
install. it's a hidden file named as .pulse. To show hidden files go to
"View" in the file browser, and check "Show Hidden Files".
I've just opened synaptic on my Lenny install, and checked to install
pulseaudio. I've not gone ahead with it, as I don't want pulseaudio, but this
is what synaptic is going to do. See below.
To be removed
esound
To be installed
gnome-audio
gstreamer0.10-pulseaudio
libasound2-plugins
libgconfmm-2.6-1c2
libglademm-2.4-1c2a
libpulse-browse0
libpulse-mainloop-glib0
libpulsecore5
padevchooser
paman
paprefs
pavucontrol
pavumeter
pulseaudio-esound-compat
pulseaudio-module-gconf
pulseaudio-module-hal
pulseaudio-module-x11
pulseaudio-module-zeroconf
pulseaudio-utils
It may be worth looking in synaptic to see if any of these packages are still
installed since you removed pulseaudio, and if so remove them. Also
re-install the esound package, although I'd disable it post install in Gnomes
sound settings.
Again. You should not need any specific sound servers to be installed to use
audio apps. All audio apps should be able to use Alsa directly. The exception
may may be audio apps that are OSS based, but installing the alsa-oss package
should handle those.
Of course you could always just reinstall Lenny, and start afresh, but I don't
like to suggest that, as it sounds too much like what is suggested when a
Windows install screws up.
Nigel.
Reply to: