Re: [orca-list] Can pulseaudio be made to work with consoles and Orca at the same time?

[Michael Whapples <mwhapples aim com>]

Hello,
I believe these "supposed security implications" are recognised by 
pulseaudio and the recommendation not to run as a system process is also 
in the pulseaudio documentation. Its this don't run as a system service 
which really puzzles me with pulseaudio, we're dealing with a system 
resource yet we're limiting it to a user resource, why? Nobody has ever 
given a good answer (I am not sure if anyone has attempted to answer) 
that question, and due to this it really adds complications to the audio 
system particularly when trying to do something as simple as having 
software speech output from orca and speakup, with no clear reason for it.

In my experience ALSA perfectly meets my needs, I have heard good things 
about OSS4 which should solve many of the issues with OSS3 (the lack of 
software mixing being an important one for us), so my advice would be 
steer clear of pulseaudio unless you enjoy problems.

Michael Whapples
On -10/01/37 20:59, Jacob Schmude wrote:
> Hi
> To do what you wish, you will have to change the configuration in /etc/default/pulseaudio to launch a 
> system-wide daemon rather than a per-user session of Pulse. Following that, you will need to add any users 
> you wish to be able to communicate with Pulseaudio to the pulse-access group so they will have permission to 
> use the audio. It's a simple enough configuration though Ubuntu doesn't use it this way by default due to 
> supposed security implications.
>
>
>
> On Jan 1, 2010, at 05:07, Bill Cox wrote:
>
>    
> > I'm trying to get a basic Karmic system working with the two critical
> > applications for the blind: Orca and speakup.  Pulseaudio is being a
> > huge PITA.  Whether I use espeakup or speechd-up, pulseaudio is
> > launched as another user as soon as the speakup module starts during
> > boot.  However, when the user logs into gnome, another instance of
> > pulseaudio is created.  The first one locks the sound card, and the
> > second is mute.  Orca wont talk.  If I kill the first one, Orca comes
> > up talking, but then my Ctrl+Alt+F[1-6] consoles stop talking.
> >
> > Any basically usable Linux system for the blind needs Orca and speakup
> > working together.  Pulseaudio, SFAIK, only allows one instance to use
> > the sound card at a time.  Pulseaudio also requires each user to have
> > his own copy.  Speakup runs before any user logs in, and therefore
> > must run as it's own user.
> >
> > Therefore... pulseaudio can't work on any truely accessible Linux box?
> > Is this basically true?  If this can be fixed, which peice of code
> > needs fixing (I'm willing to fix it)?  Should we try and make multiple
> > instances of pulseaudio play nice together so they can share the sound
> > card?
> >
> > Bill
> >
> > --
> > Ubuntu-accessibility mailing list
> > Ubuntu-accessibility lists ubuntu com
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
> >      
>     The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is 
> that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or 
> repair.
>   --Douglas Adams
>
>
>
>