[orca-list] IMPORTANT: Testing needed for a patch to fix how Orca starts/restarts

[Joanmarie Diggs <joanied gnome org>]

Hey guys.

In the process of cleaning up some old/not-quite-right code a while back
in how Orca is started/restarted, we found a bit more
old/not-quite-right code, the latest symptom being that doing an 'orca
-v' (and a few other such commands) were completely killing Orca. :-(

Juanje and I were looking at it, and tag-teamed a solution. As we were
going over things, we noticed some other behaviors which -- at least in
my opinion -- are not desirable, such as:

1 Invalid commands ('orca -z' for instance) cause Orca to not even be
started. Basically, making a typo whilst launching or restarting Orca
could be fatal.

2. Any "fatal" mistake caused Orca to dump out the full set of usage
info, rather than telling you where you went wrong.

After a bit more hacking.... I have just attached a patch [1] to bug
628256 [2] which I believe solves the above issues. That's the good
news. The bad news is that it's a significant enough change and includes
a couple of new strings. Thus, it either needs some significant testing
between now and Monday afternoon, or the bulk of the fix will need to be
postponed until after the 2.32 final, stable release.

I'll leave it up to y'all. Please test thoroughly, and also weigh in on
whether or not we postpone these changes until we start on 3.0.

Thanks in advance guys! As always, I really, really appreciate it!
--joanie

[1] http://bugzilla-attachments.gnome.org/attachment.cgi?id=169027
[2] https://bugzilla.gnome.org/show_bug.cgi?id=628256