Ubuntu-accessibility Digest, Vol 54, Issue 23

[Kenny Hitt]

Hi.
Just to clarify something: my attitude isn't directed at any of the people who have asked me
questions about my Orca crash.  My attitude comes from the fact I can debug
Linux kernel code but can't debug a fucking gnome screen reader.
In my opinion, switching to Python from C was a mistake for a screen reader.

          Kenny

On Mon, May 24, 2010 at 05:26:13AM -0500, Kenny Hitt wrote:
> Hi.
> On Mon, May 24, 2010 at 10:16:36AM +0000, Valdis wrote:
> > ...
> > > Actually, that isn't my problem with Gnome.  My problem is lack of stability
> > and slow response.
> > > My time in Gnome usually ends when Orca crashes and nothing I try can get it
> > to restart.  At that
> > > point, anything in the Gnome session is lost.  My only option is to kill the
> > Xserver and clean
> > ...
> > can you start orca with wollowing command:
> > orca >~/orca.log 2>&1 &
> > 
> > And then check what appears in the log file?
> > 
> no,  when it crashes, nothing I do can get it to restart.  Before you ask, it isn't a tts
> issue since speech-dispatcher is still up and running.
> I've been running Linux for 10 years now, so I'm not your normal stupid Windows user.
> I know how to debug problems.  Like I said in my earlier post, if this were a C program
> I would already have filed the bug report.  The fact you can't easily debug a Python
> app is a big weakness in Orca.
> I don't have enough disk space to just leav the debug options in Orca enabled either, so this
> will likely be a bug that won't get resolved any time soon.
> 
>           Kenny
>