Re: [orca-list] Orca and Acrobat Reader not cooperating



Hi All:

Two quick comments:

1) Acroread has issues.  http://live.gnome.org/Orca/Acroread

2) Getting behind Evince accessibility might be better in the long run. http://bugzilla.gnome.org/show_bug.cgi?id=309015

I have it on my list to try to allocate some GNOME a11y $$$'s to the Evince accessibility task and will send out some feelers.

Will

Jacob Schmude wrote:
Hi
I've had this happen on occasion as well, but this is the first time I've ever been able to reproduce it reliably. I'm not sure what to file a bug against, orca? at-spi? Or is this particular issue a bug in acrobat reader that is triggering something else? Also, how high should I set orca's debug level to get the information nneeded? Setting it to all, while it captures everything, yields a debug log of 248k just from starting orca to starting acrobat reader and exiting it. I'd think that might be a bit too much information :).


On Jan 29, 2009, at 12:41, nolan wrote:

This doesn't help directly with your issue, but I have experienced this behavior with other applications, though I've been too lazy to set up orca's logging to help debug it, especially as I can't reliably duplicate it. If you can, though, I hope you file a bug report. :)

Sometimes it seems like apps block all accessibility information. This isn't quite the "closing windows locks up the desktop" issue, because I can still use the desktop, and if I use my terminal hotkey, kill Orca and then usually restart Speech-dispatcher for good measure, I get speech back. I notice that it often seems to happen with Firefox, but I can't reliably duplicate it as you can.


On 01/29/2009 10:47 AM, Jacob Schmude wrote:
Hi List
I'm experiencing this in both Ubuntu 8.10 and the 9.04 alpha. I've tried both the packages from Adobe and those from the Medibuntu repositories with the same result. When I launch Acrobat reader the first time, I can accept the license agreement. When I do so, however, Orca no longer speaks. Relaunching Orca doesn't help, and the only thing that does is killing the Acrobat reader process. From then on, launching Acrobat reader triggers this. I've had the screen looked at and can verify from my system's behavior that nothing is locked, including Acrobat reader itself. It seems almost as though Acrobat reader is somehow blocking accessibility information from getting to Orca, though I'm not sure if that's even possible. I can do nothing with Orca until the acrobat reader process is killed, but my system operates normally in every other way. One interesting fact, and no idea if it's relevant, but I need to send a sigkill to the acroread process, simply using the kill command is not enough. This is with Acrobat reader 8.1.3, is there another version I should use? Or is something else happening? Any ideas?

Thanks



The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.
   --Douglas Adams

_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca


The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.
    --Douglas Adams

_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca




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