https://issues.apache.org/ooo/show_bug.cgi?id=123640
--- Comment #9 from James Teh <[email protected]> --- (In reply to V Stuart Foote from comment #8) > do you think that some of the issues > with "corrupt" systems commonly reported by folks on the NVDA support lists > (nvda@freelist and [email protected]) could be this issue with > oleacc.dll and oleaut32.dll registration? Very possibly. However, I'm pretty sure Symphony had this bug as well, and while I did see brokenness for the current session, a reboot seemed to fix it, suggesting Windows somehow restored the oleacc registration itself. > The recent tone on both lists has been to stay away from ia2 beta testing as > it has just gotten too painful. Is it worth it and can you think of a way to > coax them to resume testing? I did try to do this with my suggestion on our lists that new builds should have resolved this issue. If it broke someone's system, they probably would have asked for ideas on how to fix it already, so I don't think it's worth posting general recovery instructions unless people ask. The important thing is to make users aware that this is now fixed. That said, bug 123643 is a fairly big obstacle to wider testing. It's very difficult for screen reader users to enable AT support manually. It can be done with a registry patch, but the patch needs to be somewhere easy for users to find and download and the whole process tends to make many users shy away. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
