Re: [orca-list] Help - Orca is Broken for Me!!!

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I don't even use brltty though.  In the past, I guess this never came
up but when I fell back to an older git version, I guess it didn't go
back far enough or something because I still can't get it to work.  I
guess I'll try and reinstall the original dropline-gnome version of
orca and see if that will go.  Dropline-gnome for slackware is a
2.24.3 release or something.

Oh, thanks for the quick replies on this.

On Sun, Jun 07, 2009 at 04:41:29AM -0400, Willie Walker wrote:
> Hi Steve:
>
> BrlTTY/BrlAPI have been providng a set of Python bindings for a long  
> time (BrlTTY 3.8, I believe).  Prior to this, we had a custom  
> Orca-specific brl module for BrlAPI.  It was a hairball and prevented us  
> from doing a lot of things with braille.  For the 2.27.x cycle, I made  
> the decision to dump the old brl module in favor of using the Python  
> bindings provided by BrlAPI:
>
> http://bugzilla.gnome.org/show_bug.cgi?id=581352
>
> Looks like I ended up making a hard dependency on BrlAPI's python  
> bindings (sorry), and I've reopened the bug.
>
> BTW, when working from the latest sources in GIT, I would not recommend  
> that you ever replace the Orca under /usr until you are sure the latest  
> sources are working properly.  What I do is run autogen.sh with a  
> command line option of --prefix=`pwd`/bld instead of --prefix=/usr. When 
> I then do a make install, I can run Orca via the bld/bin/orca that will 
> be created under the source directory.
>
> Will
>
> We made some changes to
> On 06/07/09 04:23, Steve Holmes wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: RIPEMD160
> >
> > I just did a git-pull from git://git.gnome.org/orca, notice that the
> > Changelog shows the most recent changes, I did a .autogen.sh
> > - --prefix=/usr, make, and make install and all appeared good so far.
> > However, When I do a 'startx' to start up my gnome session, Orca
> > fails.  I included a copy of the trace back below.  Does anyone know
> > what other changes I might need to make to get this to work again?  Up
> > til now, Orca worked fine with gnome-speech and espeak So basically,
> > the only thing that has changed on my box is Orca itself.  I also did
> > a new update to at-spi from same git address but I still get the same
> > trace-back.
> >
> > - ----- Begin Error Log -----
> > Traceback (most recent call last):
> >    File "<string>", line 1, in<module>
> >    File "/usr/lib/python2.5/site-packages/orca/orca.py", line 54, in<module>
> >      import mouse_review
> >    File "/usr/lib/python2.5/site-packages/orca/mouse_review.py", line 44, in<module>
> >      import braille
> >    File "/usr/lib/python2.5/site-packages/orca/braille.py", line 90, in<module>
> >      command_name[brlapi.KEY_CMD_FWINLT]   = _("Line Left")
> > NameError: name 'brlapi' is not defined
> > DBus connection has been lost, trackerd will now shutdown
> > tracker has exited (reindex = 0)
> > Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
> > <unknown>: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
> > Window manager warning: Could not find display for X display 0x81126c0, probably going to crash
> > Bug in window manager: IO error received for unknown display?
> > nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
> > The application 'nm-applet' lost its connection to the display :0.0;
> > most likely the X server was shut down or you killed/destroyed
> > the application.
> > gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
> > gnome-session[29283]: WARNING: Failed to send buffer
> > gnome-session[29283]: WARNING: Failed to send buffer
> > The application 'gnome-session' lost its connection to the display :0.0;
> > most likely the X server was shut down or you killed/destroyed
> > the application.
> > xinit:  connection to X server lost.
> >
> > waiting for X server to shut down
> >
> > - ----- End Error Log -----
> > The messages after the trace-back are from when I did a
> > ctrl-alt-backspace to kill the X session.
> >
> > Any help would be greately appreciated.
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.9 (GNU/Linux)
> >
> > iEYEAREDAAYFAkoreRQACgkQWSjv55S0LfH+sgCg51LSJHVKtvLQM2MEExw4KRJM
> > TcEAoK4dzLTfS3TuArv8vsT2vg3y6mVM
> > =T1/V
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Orca-list mailing list
> > Orca-list gnome org
> > http://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
>
> _______________________________________________
> Orca-list mailing list
> Orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkorgPUACgkQWSjv55S0LfHNvQCg51Nfd32d3Vcf7fzHN+UHhC+D
6xQAn2L3yjdYgzDo1+b22DMEICHx9NWr
=pNRM
-----END PGP SIGNATURE-----