Re: Gnopernicus 0.7.0 does not want to init my brl display

["Tom and Esther Ward" <tward1978 earthlink net>]

Hi, Delaunay.
There is a known bug with gnopernicus 0.7.0 which ships with Drake where the
braille support is broken. You must download 0.7.1 from gnome.org and
rebuild ggnopernicus from that in order to get braille support.

----- Original Message -----
From: "Delaunay Christophe" <christophe delaunay thomson net>
To: "Gnome Accessibility List (E-mail)"
<gnome-accessibility-list mail gnome org>
Sent: Tuesday, December 16, 2003 5:58 AM
Subject: Gnopernicus 0.7.0 does not want to init my brl display


> Hello listers,
>
> From the console, when I type startx, gnopernicus starts talking but does
> not want to initialize my braille display.
>
> I know that this question seems like a faq but before asking for your
help,
> I made sure twice I really did all what I read in the documentation.
>
> So, here is my configuration :
>
> - linux mandrake 9.2 on a Compaq DeskPro with 512 mb of ram and PIII
> processor running at 750 mHz;
> - brltty rev. 3.3.1 compiled with --enable-api and driving a
> braillex ELba, (Papenmeier braille display with 32 cells);
> - gnopernicus 0.7.0 with all gnome accessibility features installed,
> comprising the java access bridge.
> - The used TTS is festival 1.4.3 but due to problem with my
> soundboard, it really speaks too fast, (like a tape going twice its
speed).
>
> When I launch "startx", gnopernicus is really launched and begins to speak
> but here is what I receive on stderr.
> -------------------
> **********************
> * SCREEN READER CORE *
> **********************
>
> GTK Accessibility Module initialized
>
> brl_open_device: open device failed
> ** BRAILLE initialization failed for BRLTTY on port 1
>    To change one or more settings use gnopernicus UI
>
> (srcore:5924): gnopernicus-WARNING **: Callbacks are NOT supported by "V0
> Kevin - Festival GNOME Speech Driver" voice.
> gnopernicus-Message: speech initialization succeded
> -----------------
>
> First, I checked for the presence of /etc/brlapi.key. It's really here and
I
> can read it.
>
> Then, I used the "gconftool-2" command as stated in brltty's
> "README.gnopernicus" file in order to let gnopernicus use the brltty API.
>
> Then, I wrote a .xinitrc file in my home directory as follows :
> --------------------
> #!/bin/sh
>
> # Define environment variables.
> GARNOME=/usr # garnome is not installed on this computer
> PYTHONPATH=/usr/lib/python2.2/site-packages
> GDK_USE_XFT=1
> GTK_MODULES=gail:atk-bridge
> export PYTHONPATH GDK_USE_XFT GTK_MODULES
>
> # Configure Gnome.
> gconftool-2 --type bool --set /apps/desktop/gnome/interface/accessibility
> true
>
> # Tell Gnopernicus which virtual terminal is being used by the X display.
> # This is a bit complicated so cut-and-paste (rather than retype) it.
> CONTROLVT="$(grep "using VT number" "/var/log/XFree86.$(echo "$DISPLAY" |
> sed -e "s/^.*::*\([0-9]*\).*$/\1/").log" | sed -e "s/^.*using VT number
> \([0-9]*\).*$/\1/")"
> # I added next lines to print the value of CONTROLVT
> echo -n "=*=*=* The CONTROLVT variable was set to "
> echo -n $CONTROLVT
> echo " =*=*=*"
> export CONTROLVT
>
> # Start the Gnome session.
> exec $GARNOME/bin/gnome-session
> ------------------
>
> When the X session start, I can notice that the CONTROLVT variable is set
to
> 7.
>
> So, what may be causing this braille initialization problem?
>
> Is there a way in which gnopernicus could be more precise at init time
when
> an error occurs?
>
> Many thanks in advance. Have a nice day. Chris
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
>