trouble getting Orca and Ubuntu to work

Monty monty-ubuntu at bc.cx
Tue Feb 6 12:02:38 GMT 2007


Hello All,

Recently I have had an inclination to branch out from my usual CLI-based 
Debian/Linux environment and try out Gnome and Orca since it would seam 
that it is definitely on the right path for an accessible X-windows 
environment.  Another motivation is that I would like to get VMWare up and 
running as well.

During my exploratory phase, I thought it would be wise to check out an 
Ubuntu Live CD so everything could remain self contained and not mess with 
my regular system.

My first attempt was with the Edgy V6.10 Live CD.  Unfortunately  it did 
not work as advertised.  As per the instructions, I booted with the CD, 
waited until the boot prompt, pressed F5, 3, <enter>, and waited the 
several minutes for the desktop to appear.  At this point no Startup wav 
file (the Ubuntu sound byte), and no Orca.  I did have sighted assistance 
confirm that there were several GTK/scripting errors.  (not sure what as 
there were loads of them)

I then tried booting without accessibility with an intention to trying the 
CTRL+Alt+F2, orca <enter> method since it has been suggested this is 
necessary at times.  This method does seam to work somewhat better than 
the former as I did get the Ubuntu Startup sound-clip without any startup 
errors to my knowledge.  CTRL+Alt+F2 followed by orca <enter> did 
successfully load and start orca.  The welcome message  and the 
configuration questions all worked fine.  It then says "you must logout 
and login for settings to take affect" followed by something like: 
"Switching to function tracking mode" (could have that wrong it's been a 
couple of days) and sits there doing nothing.  I tried to perform a 
CTRL+Alt+BackSpace but that too did nothing.

Just last night I downloaded and burned the daily build of the Feisty live 
desktop/I386 CD and it didn't seam to work either.  I haven't played with 
the Feisty live CD too much yet though so maybe something will work.

I would be interested to find out if others have experienced any of the 
above or may have some kind of idea why it isn't working or what I am 
doing wrong?  Messages in this and other archives imply others have had no 
problem.


Thanks for any light shed on this,
   Monty



More information about the Ubuntu-accessibility mailing list