Re: gnopernicus and braille display not working

[Kenny Hitt <kenny hittsjunk net>]

Hi.

You need to set the CONTROLVT variable to tell BRLAPI the virtual
console of the X server.

export CONTROLVT=7

That tells BRLAPI my X server is on virtual console 7.  If you use gdm,
add the line to your ~/.gnomerc.  If you use startx, add the line to
what ever file you use to start Gnome.  When I used startx, I used a
.xinitrc file in my home dir.  If I used startx, I would add the line at
the top of my .xinitrc file.

Be aware you will need to rebuild your Gnopernicus replacing the
ttybrl.c file in the Gnopernicus source withe the one found in the
latest svn of Brltty to get any real use out of Gnopernicus's braille
support.

Debian's Brltty is still at 3.4.  You might also need to upgrade your
Brltty.  I have upgraded both my Gnopernicus and Brltty, so I don't know
how good your results will be using Debian's packages.

Hope this helps.
          Kenny
	  
On Wed, Apr 13, 2005 at 09:03:21AM +0200, Jan Buchal wrote:
> Hello,
> 
> I use gnopernicus Debian package version 0.9.19-2 and brltty Debian
> package version 3.4.1-3. In gnopernicus I have setup brltty's api however
> braille show any message, empty screen.. I do not see any errors in
> .xsession-erros. See bellow. Can you help me?
> 
> Xsession: X session started for buchal at St dub 13 09:28:44 CEST 2005
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> SESSION_MANAGER=local/freebsoft:/tmp/.ICE-unix/10677
> GTK Accessibility Module initialized
> Bonobo accessibility support initialized
> 
> **********************
> * SCREEN READER CORE *
> **********************
> 
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> BrlAPI detected a 40x1 display
> Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> 
> ** BRAILLE initialization succeded for BRLTTY device on port 1.
>    To see something you must have a Braille device connected to your computer.
>    To change one or more settings use gnopernicus UI.
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: You are using at least one voice witout markers
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to register the callback
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> 
> (srcore:10747): gnopernicus-WARNING **: Unable to find parameter
> gnopernicus-Message: inicializace řeči uspěla
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
> 
> 
> 
> 
> 
> 
> 
> -- 
> 
> Jan Buchal
> Tel: (00420) 224921679
> Mob: (00420) 608023021
> 
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list