Re: [orca-list] The Jupiter console screen reader

["B. Henry" <burt1iband gmail com>]

I think -D with a capital D is probably what is /was meant, but not sure. 
-D says it is a boolian option, so not sure if that means you must use some thine like -D=1 or -D=yes or to 
turhn of daemonizing 0 or no.
I've not tried this yet/but mayb try here in a few/just guessing from a quick glance at the manpage for PA.


-- 
     B.H.
   Registerd Linux User 521886


  Storm Dragon wrote:
Wed, May 11, 2016 at 11:34:29AM -0400

> Howdy,
> I must have done something wrong with the pulse configuration, case when I tried it, I got errors and now 
> sound. Here's exactly what I did:
> created file ~/.config/pulse/default.pa
> .include /etc/pulse/default.pa
> load-module module-native-protocol-unix auth-anonymous=1
> socket=/tmp/pulse.sock
>
> sudo su - root
> cp /etc/pulse/client.conf /root/.config/pulse/client.conf
> Edit /root/.config/pulse/client.conf, and appended the following line to the end of the file:
> > ; default-server = unix:/tmp/pulse.sock
>
> It keeps saying there is no option -d with pulse. but running pulseaudio -k follow by pulseaudio causes 
> loss of sound, until I remove the ~/.config/pulse/default.pa file. So, did I do something wrong? Sorry for 
> being so slow on the utake lol.
> Thanks
> Storm
> On Tue, May 10, 2016 at 06:01:38AM +0200, Peter Vágner wrote:
> > Hello,
> >
> >
> > I've attempted to explain it in an earlier conversation. Jupiter
> > uses espeakup for software synth support the same way speakup does
> > so as far as sound output is concerned there should be no
> > difference.
> >
> >
> > I'll try to put this gently one more time with as precise steps as I can.
> >
> >
> > If you wish to use desktop i.e. gnome and mate, run pulseaudio as
> > a part of that desktop, then change your mind and with the desktop
> > still running fire up one of the virtual consoles, start espeakup
> > or jupiter, this is pulseaudio configuration that is working for
> > me.
> >
> >
> >
> > As a normal user i.e. the one running the pulse audio, create a file
> >
> > ~/.config/pulse/default.pa
> >
> > with the following content
> >
> > .include /etc/pulse/default.pa
> > load-module module-native-protocol-unix auth-anonymous=1
> > socket=/tmp/pulse.sock
> >
> >
> > Now as a root user create a file
> >
> > /root/.config/pulse/client.conf
> >
> > you might like to do
> >
> > cp /etc/pulse/client.conf /root/.config/pulse/client.conf
> >
> > And make sure this is configured in that file
> >
> > ; default-server = unix:/tmp/pulse.sock
> >
> >
> > Restart pulseaudio on your desktop by relogging, restarting or doing
> >
> > pulseaudio -k
> >
> > pulseaudio -d
> >
> >
> > And you should be good to go.
> >
> >
> > Security concerns are there that anyone with ability to gain root
> > privileges can manipulate your sound devices you are using as an
> > user, however if we are tallking security here, anyone with root
> > privileges can kill your pulseaudio instance for that matter and
> > do what they want.
> >
> >
> > I understand proper fix is to make it so that espeakup is not
> > running as root, possibly speakup and jupiter are not running as
> > root but as your normal user with their respective device
> > permissions controlled by udev so it can access it.
> >
> >
> > Greetings
> >
> >
> > Peter
> >
> >
> >
> >
> >
> >
> > On 10.05.2016 at 01:08 Luke Yelavich wrote:
> > > On Tue, May 10, 2016 at 08:38:00AM AEST, kendell clark wrote:
> > > > hi
> > > > If I can get this going, I'll package this for sonar and replace speakup
> > > > with this, assuming it doesn't have the same problem both of these have,
> > > > and that is getting sound through pulse audio as root.
> > > I would honestly investigate this further before just blindly replacing
> > > it... Maybe as an alternative, but not right out replacing, and thats
> > > not really possible anyway, since speakup is part of the mainline kernel,
> > > even if only in staging.
> > >
> > > Luke
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > > Orca documentation: https://help.gnome.org/users/orca/stable/
> > > GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> > > Log bugs and feature requests at http://bugzilla.gnome.org
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > Orca documentation: https://help.gnome.org/users/orca/stable/
> > GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> > Log bugs and feature requests at http://bugzilla.gnome.org
>
> -- 



> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org

End of quoted content