Re: [orca-list] broken accesibility (was help building at-spi)

[Steve Holmes <steve holmes88 gmail com>]

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

That environment sounds so old and out of date! If I had half those
experiences, I would consider completely re-installing the system with
a more current distro.  Last year I had similar problems, not with
being so out of date but I messed with Debian Unstable and didn't know
what I was doing when I tried down grading some packages.  I ended up
being unable to start X, let alone any other parts of gnome.  I then
decided it would be easier to just start over and of course make sure
all my valuable data was backed up.

I have to say with all those experiences and even a busted Debian
Unstable, Speakup rolled along in the console beautifully and didn't
skip a beat.  That's another reason I value having console access;
Xwindows can break just like the other Windows we learn to know and
hate but the text console running a Speakup modified kernel or loaded
modules is solid as a rock!

On Tue, Jan 05, 2010 at 09:59:14AM -0500, aerospace1028 hotmail com wrote:
> greetings,
> I have busted accessibility on my ubuntu hardy machine.
>
> When attempting to build orca (2-22) from the git repository, I ran into some problems at the at-spi step.  
> First autoconf claimed my intltool was too old (it wanted 0.40.0 and I had 0.37.1).  After failing to 
> successfully build intltool0.40.0 from source, I was able to get intltool0.41.0 to install from the karmic 
> repositories onto my hard machine.  This time whe running "./autogen.sh --prefix=/usr 
> --libexecdir=/usr/lib/at-spi", autoconf issued an error that my dbus-glib-1 was out-of-date.  Again I 
> managed to isntall libdbus-glib-1-2 and libdbus-glib-1-dev from the karmic repositories.  Now at-spi did 
> build and install and I moved onto orca.
>
> pulling and building orca from git provided no obsticles.  As I did with atk, and at-spi, after git clone, 
> I performed a git checkout -b origin/gnome-2-22 (since I'm running gnome-2.22).
>
> After finishing the make install on orca itself, I quit my running orca and relaunched it from the run 
> dialog.  I returned to the gnome-terminal to double-check I had the new orca.  To my surprise, "orca 
> --version" claimed I was running 2.29.4 (not the 2.22.3 I had expected).
>
> I did a little exploration to see if I could find any major issues with this mis-matched gnome and orca 
> combination.  For the most part, it seemed to be working (there were some parts of the openoffice dialogs 
> that couldn't be read, but I'm used to that).
>
> I had to shut down my machine and leave for a while.  When i booted back in, after entring in my ID and 
> password, an error message popped up saying that at-spi was requested by this session, but at-spi was 
> unavailable (according to some sighted assistance).  I had some sighted assitance click the "OK" button 
> (pressing ENTER on the kyboard did nothing).  When the desktop came up, orca was there (kind of).  I could 
> still get feedback in the gnome-terminal, bu orca would ot read the menus in the top panel of the desktop 
> nor the run dialog.
>
> I double-checked in the atk, at-spi and orca build directories and all three said the working branch was 
> 2-22.  In all three cases "git branch" only listed master and 2-22 (with the asterisk in front of 2-22) and 
> "git status | head -1" confirmed origin/gnome-2-22 was the working branch.
>
> I proceeded to run make uninstall in all three build directories.
>
> I then tried to install atk and at-spi, but apt said they were already the newest versions.  I forced a 
> "apt-get --reinstall install atk at-spi".  I paid close attention and confirmed that both were installed 
> from the hardy repositories.
>
> However, when I went to the shutdown menu item and tabbed to where the log-out icon should be, I did return 
> to the log-in screen; but again when I entered in my ID and password, I got the at-spi unavailabel message. 
>  Entering in "orca" or "/usr/in/orca" in the run dialog failed to bring up any speech (it did not say these 
> were invalid entries: I could see the dialog box disappear as if these programs were actually launched).  
> When bringing up the gnome-terminal, I tried orca -t.  I did not get the speech output I normally get, and 
> I did otice some text pop up, but it didn't appear to be the long list of language options; it only took up 
> two-three lines.
>
> At the moment, I don't have any orca capacity on my ubuntu machine.  Does anyone have a clue how I can fix 
> this?                                        
> _________________________________________________________________
> Hotmail: Trusted email with powerful SPAM protection.
> http://clk.atdmt.com/GBL/go/177141665/direct/01/

> _______________________________________________
> 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
> Log bugs and feature requests at http://bugzilla.gnome.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAktDdhwACgkQWSjv55S0LfHKwwCgzZV7qwXnZGJ62Q75zbC5sQl0
opsAoNMzlvas2954De+mc03orxqyYB0j
=yhxL
-----END PGP SIGNATURE-----