Howdy James, howdy list,
This might be off topic but maybe for some interesting as well... I am running ubuntu Mate 18.04 LTS and am running Fenrir successfully.
Once you have all dependencies installed, the trick to get speech working for me in the console, was to run Fenrir with sudo.
Right, fenrir needs access to special device files in /dev/vcsa[1-6] Where it gets its information from. Fenrir also needs access to /dev/input/* To get the shortcuts and consume them and to /dev/uinput To send the non shortcuts input to the system I am still working on running Fenrir without needing sudo
Really? This is amazing and interesting! You should give a talk to storm_dragon here. He is currently working on an script to make fenrir rootless. The trick will be correct and finetuned permission setup of the needed files to the user what runs fenrir or an fenrir group or similar. IMO a screenreader should have as less permissions as possible because it gets many sensitive data. all screenreaders are keyloggers and session recorders by design to be able to do its job. So the software should restricted where ever possible. I m all in here and help where i ever can... run those stuff as root and even higher should not be done those days anymore. I very like orcas and AT-SPIs concept here. Lets fix fenrir up :).
Just remember to turn off Orca when in the terminal.
This is not needed, fenrir has the abilities to go away if you switch to GUI and come back if you move to TTY. If you use logind its enabled and autodetected by default. If not you can set screens to ignore / suspend in settings.conf or you can communicate it with an script or something via unix socket at runtime to fenrir.
Small tipp: fenrir -e Doesn’t require root as well and you can make orca prevent from double output using xterm or konsole (or any other inaccessible terminal emulator). Those are exclusive visible to fenrir then. So orca and fenrir coexist in a nice way then on GUI too even if they are in same session.
Cheers chrys
Hi folks
On 08/07/2019 20:34, Storm Dragon wrote:
I'm not sure how easy it is to get Fenrir running on Ubuntu
though, this may be the one drawback.
I am running ubuntu Mate 18.04 LTS and am running Fenrir
successfully.
Once you have all dependencies installed, the trick to get
speech working for me in the console, was to run Fenrir with sudo.
You can run the following from a graphical terminal and then
swtich to a console with Control+AltFF1 through F6:
sudo fenrir
I am still working on running Fenrir without needing sudo and
have also had some success using Fenrir with the 'e' option. This
allows Fenrir to run in the graphical terminal.
Running sudo fenrir-daemon also runs Fenrrir as a background
process, allowing you to use your terminal for other things while
Fenrir is running. Just remember to turn off Orca when in the
terminal.
Best
James
Howdy
Norman,
This is another good reason to use Fenrir. There is a script you
can run in /usr/share/fenrirscreenreader/tools/configurepulse.sh
that will make it so you will have sound in the console.
I'm not sure how easy it is to get Fenrir running on Ubuntu
though, this may be the one drawback.
Thanks,
Storm
On Mon, Jul 08, 2019 at 11:57:35AM -0400, Norman wrote:
Hi.
I use the defaults for ubuntu mate 18.04
On 7/6/19 2:32 PM, Didier Spaier wrote:
Hello Norman,
The ability of Orca to to read aloud what's displayed on a
terminal
mostly depends on which terminal is used.
So which one do you use? And which distribution/version?
Generally speaking, console based apps can benefit of console
screen
readers like speakup, fenrir or speechd-up that are intended
to be used
in a console, not in a graphical environment.
Their availability depends on which distribution and version
you use.
However, from a quick look at the screenshots provided by the
project I
am not optimistic as a lot of information are displayed on
sub-windows,
including arrays between them and I don't know how a screen
reader can
present this information (I am sighted).
Good luck,
Didier
On 7/6/19 8:03 PM, Norman wrote:
Hello all.
I sometimes need to use a terminal based program called
sngrep to trace voip calls from my personal pbx. However,
orca struggles with this program, it doesn't read everything
and scrolling is a big issue. I was wondering, are there any
helpful tips people have when using orca with console based
programs? or would a second screen reader like speakup do
better at this?
I'd like to try speakup and find out but can't find any good
docs on how to make it work.
Can anyone help?
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
|
