Re: Orca 0.2.4 setting issue



Tim Miao wrote:
Sorry,  "orca --text-setup" doesn't work for me either.

I'm not sure why this happens. It's strange. After installation of vermillion_42 on snv_41, I could find /usr/bin/orca while others of my colleagues in Beijing Team can not find it on their box. So I went to orca download page and got the latest orca 0.2.4 source code, installed it on my box with default configure settings. The orca was installed to /usr/local/bin/orca. I tried to invoke the orca gui setting dialog with "/usr/local/bin/orca --gui-setup", but failed. I removed all the files and directory in my home directory which was created by /usr/bin/orca-setup. Then I run the /usr/local/bin/orca --text-setup again, it still doesn't work. I tried to generate the .orca directory in my home directory with /usr/bin/orca-setup, and uncommented those three lines, run /usr/local/bin/orca --text-setup again, the output listed below:
##################
bash-3.00$ /usr/local/bin/orca --text-setup
GTK Accessibility Module initialized
Changing debug level to 1000
Changed debug level to 1000
Changing debug level to 0
Changed debug level to 0
##################

orca gui preference still failed to start.

Okay, I think I understand now. Even if you are starting the new version of
Orca from CVS (the one you installed in /usr/local/bin), Python is still getting the rest of it's installed .py files from under /usr/lib/python2.4/ (the new ones would have
gone under /usr/local/lib/python2.4). These would be the old ones.

The best thing to do is to reconfigure Orca from the CVS source code with

autogen.sh --prefix=/usr

then when you do the "make install" it'll overwrite the ones under /usr.

For extra bonus points, you can remove the Orca files under /usr/local
so it will reduce confusion in the future.

Thanks.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]