| ï
Dear users,
As i mentioned in my previous
E-mail, Ubuntu 10.04 is being intensively developed. The development
release is still containing some bugs, which would have to be debugged. But, and
this is very important for user testing, Installation can now be completed
without I/O error message, but I AM afraid, that core engine of Ubiquity is
registering incorrectly some GTK and at-spi related components to The database,
because some parts of Gnome are totally unaccessible. This problem is not being
occurring, while intensively testing latest development snapshot in live CD
mode. User can not access whole Gnome menu after finishing The installation,
user can not use The run dialog, but attention! The menus and dialog windows are
being correctly displaied on The computer screen. Only Orca can not get
necessary feetback from some subsystems.
But this all is only presented, if Ubuntu has been
installed. While working with it on live CD mode, everythink is working OK. I
will compare issues with some crucial variables, which are being used by Orca
while using build in structual navigation and even arrow keys. If those semantic
errors are only presented after Ubuntu installation or even in live CD mode.
Now, if i want to use some WEB page which is requiring The precise arrow key
navigation, it is big fight. For example, while working with
WEB site, i Am not able to correctly navigate by
using FOur number by The headings number four and even arrow keys support is not
working correctly. So i must disable Orca Gecko caret control by pressing Orca
modifier key and function key 12. Andi also must turn on The keyboard support
for caret movement in Firefox. Only after those procedures, i can use Orca
better, but it is not soft work.
But i AM not occurring random crashes of
at-spi-registry, only while working with installation program while using Ubuntu
in live mode, when Orca pronounced 100 percent and The installation has been
completed dialog window appear, At-spit-registry is being finished unexpectedly
error message appeared. Fortunately, those crashes are not affecting damon,
which is being responsible for switching to The various console. So what
advanced visually impaired user can do in this cases?
Switch to The free console, typing ubuntu and enter
key tvice
Followed by typing sudo su
Followed by Enter key. And then,
killall python.
Fortunately, Ubiquity and installation program
related components are not written by using Python programming language. So
visually impaired user can even finish The installation program and, and what is
very ammazing, can even send The bug report to The developers of Ubuntu by using
application error reporting service.
So i will intensively test Ubuntu development
versions.
And where You can always find this development live
CDS?
Please follow this link.
|