https://bugs.documentfoundation.org/show_bug.cgi?id=155705
--- Comment #7 from [email protected] --- @stragu Unfortunately not, yet that might be possible somehow, I don't know... you could use the cppunit patch that and then `make CppunitTest_sw_a11y CPPUNIT_TEST_NAME=tdf155705::TestBody` which doesn't rely on AT-SPI seeing LO. The other solutions I know depend on LO being visible to AT-SPI, so might not work in your case (see below). But here are a couple: # Get Orca to read the text attributes. 1. Launch Orca 2. Open the attached sample in LibreOffice 3. Navigate to the second part of the paragraph on page 2 (i.e. put the caret there) 4. Ask Orca to list attributes (that should be Orca+f, with Orca being either CapsLock or Insert) # With Accerciser Alternatively (but I doubt that would work if the script doesn't find soffice), you could try manually using Accerciser: 1. Open the attached sample in LibreOffice, making sure the part of the paragraph on page 2 is at least partly visible 2. Open Accerciser 3. Find soffice in the app tree (which might not work then...) 4. Navigate the object tree to find the paragraph on page 2. That's gonna be at "path" 0 0 0 0 1 0 0 1, which means under soffice child 0, then child 0 of that one, etc. If there's only one paragraph in the "document text" node and you see the right one on screen, select that one. That should be enough to crash (Accerciser will query the attributes automatically to display them, and that'll crash). If that wasn't for some reason, on Accerciser's IPython Console, try `acc.queryText().getAttributes(0)`. # Debug why soffice isn't found by the escript If soffice doesn't appear to AT-SPI, I can see 3 reasons: 1. Somehow you don't have the components on your system (odd, but possible I guess?) 2. Somehow LO doesn't expose its objects (wrong VCL (gen won't work)? Somehow it disables itself in some situations I am not aware of? maybe ask Michael Weghorn) 3. You have another app running that stalls the requests on the AT-SPI bus. Unfortunately, if one app doesn't answer requests, it might just time out the whole app listing request. You can debug that with `orca -l` or in Accerciser (seeing which app is missing from the list, or again in the IPython console something like `desktop = pyatspi.Registry.getDesktop(0); [desktop.getChildAtIndex(i).name for i in range(desktop.getChildCount())]`) For the moment that's the only things I can think of. -- You are receiving this mail because: You are the assignee for the bug.
