Re: [orca-list] Latest refactor-related fixes are in master for your testing pleasure

[Steve Holmes <steve holmes88 gmail com>]

Well, I say a dialog popped up because I got the error ding right after 
typing 'orca --replace' from the run dialog.  Can't say where that 
necessarily came from but I suspected Orca since that came up 
immediately after the command.  I'll try and turn on debugging and see 
how things go.  It seems that all these errors have occurred while I had 
Thunderbird running. and more particularly when I was focused on the 
tree of mail boxes.  I use IMAP through gmail and I think when the 
losses of speech happen is when I hear the progress indication going 
while IMAP messages are being retrieved.  I have noticed for a long time 
that when Thunderbird is fetch mail, Orca tends to hang until that 
process completes.  I think this has become more unstable lately.  I'll 
have to see if I get any speech losses when Thundrbird is not running.

Yes, this is Arch Linux on my 332 bit desktop system.

On 01/21/2011 05:47 PM, Joanmarie Diggs wrote:
> Hey Steve.
>
> > speech, I get an error box that pops up. After jumping over to a native
> > console and killing Orca, I can then go back into my gnome session and
> > start orca from the run dialog without any --replace. Speech comes back
> > and then I can read the dialog. The error indicates that can't find some
> > file in my home directory but the file name is blank. That is, it says
> > that /home/steve/// cannot be found. I have never seen this error
> > before. I had this happen at least 3 times today after my recent git
> > pull from this afternoon. Once I got the error simply by leaving the
> > machine unattended for over 30 minutes and the other two times I was in
> > Thunderbird trying to read some mail.
>
> Well, that is pretty odd. Also note that Orca doesn't pop up error 
> dialogs. To be honest, we might be a bit more user-friendly if we did, 
> instead of dumping tracebacks to debug.outs assuming you happen to 
> have enabled debugging.
>
> Given that stranger things have happened, I'm not willing to say 
> beyond a shadow of a doubt that we're not causing that behavior. But I 
> cannot imagine how at the moment we might be. Or especially why 
> handling some tracebacks more gracefully would suddenly cause dialogs 
> to appear... So... Please keep me posted. And if you can capture a 
> debug.out (or any other data) that explains where that dialog is 
> coming from I'd love to see it.
>
> Is this in Arch, btw?
>
> --joanie