speakup goes oops/bye-bye on wheezy

[covici at ccs.covici.com]

OK, here is what is happening to me with pulseaudio.  Normally, I have
in my /etc/pulse/client.conf spawn=no, and things going to alsa, like
mplayer work correctly.  paplay says connection refused.  Now if I
change spawn=yes,  as a normal user both paplay and mplayer think they
are playing, but they are silent.  As root,  paplay still says
connection refused, but mplayer does work.  I am using gentoo uunstable
and gnome is not running, although dbus is running.  Anyway I can make
alsa things work and pulseaudio things work for things which must have
them?  I have the plugin installed.

Thanks in advance for any suggestions.


Jason White <jason at jasonjgw.net> wrote:

> covici at ccs.covici.com <covici at ccs.covici.com> wrote:
> > I have never gotten pulse to work at all, I had to bypass it to get any
> > audio in a text console.  If anyone knows more, I can post the details.
> 
> If you wanted to run some tests, I would suggest starting with paplay. It's
> like aplay, except that it directs output to PulseAudio directly. For Alsa
> applications, you need a configuration that directs output to PulseAudio.
> Under Debian, at least, this is provided by default.
> 
> Note that Pulse is started when a D-Bus connection is made; you don't have to
> invoke it as a daemon. There's a way to set it up to run as a system-wide
> daemon as well, but I haven't tried that. Obviously this has security
> implications on multi-user systems, i.e., one user can interfere with another
> user's audio - not a problem on most workstations these days.
> 
> _______________________________________________
> Speakup mailing list
> Speakup at linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici at ccs.covici.com