Description of problem: The problem was noticed while installing Fedora 32 Workstation from live image. Namely in Gnome on Wayland. The environmet itself works fine with Orca screen reader. But from the moment Anaconda is started, Orca stops talking completely. So even if user tries to switch to another application (Alt + Tab etc.), speech does not work. Version-Release number of selected component (if applicable): anaconda-32.24.3-1.fc32.x86_64 How reproducible: always Steps to Reproduce: 1. Boot the Live Fedora 32 Workstation installation image under Wayland session. 2. Launch Orca with Alt + Super + s (and adjust sound volume). 3. Press Insert + t (or KP_Insert + t) to test whether Orca speaks. 4. Launch Anaconda installer. 5. Press Insert + t (or KP_Insert + t) to test whether Orca speaks. Actual results: Orca says nothing and even Orca's other shortcuts (see documentation) not working. Expected results: Orca reads the content when navigation keys (tab, shift + tab, up, down, left and right arrows) are used. Additional info: The issue was discovered by Pavel Vlček (CC). I reported it, because Bugzilla also has some accessibility issues.
Related bug 1818957.
*** Bug 1880742 has been marked as a duplicate of this bug. ***
Related bug 1592361.
We've been talking about this recently, and benzea thinks he has a way to work around the problem. I'm going to test it in a scratch build shortly. Proposing this as an F34 Final FE: if we can solve it, that would be a substantial a11y improvement and I think worth an FE, obviously cannot be fixed with an update.
For the record, this is the plan: benzea: soo benzea: xprop -root -format AT_SPI_BUS 8s -set 'AT_SPI_BUS' "$( busctl call --user org.a11y.Bus /org/a11y/bus org.a11y.Bus GetAddress | sed 's/s "\(.*\)"/\1/' )" benzea: single line script installed at /etc/xdg/Xwayland-session.d/00-at-spi benzea: I hope that would do the trick benzea: well, pretty sure it'll work, and it feels pretty clean, we could even just install it as part of the at-spi package in general
So I tested a scratch build of at-spi2-core with the exact change benzea proposed - dropping a script with that contents as /etc/xdg/Xwayland-session.d/00-at-spi - and it works. Built a live image with that build, booted it, turned on orca, ran anaconda, and got screen reading. I'm not sure how navigable anaconda is for people who actually can't see the screen, to be honest, but at least the tech works. Going to mark as POST, but see exactly how much error checking Benjamin thinks might be needed :)
The error checking is not really needed, in particular in Fedora where we can blindly rely on systemd to be installed. After all, if the dbus call fails, then the a11y infrastructure is probably not functional anyway and setting the X property cannot be destructive.
okay, I guess I'll send a build just as-is then. +3 votes in https://pagure.io/fedora-qa/blocker-review/issue/357 , marking accepted FE.
FEDORA-2021-89f1fdaefd has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-89f1fdaefd
FEDORA-2021-89f1fdaefd has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-89f1fdaefd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-89f1fdaefd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Can folks please test and karma the update? I did test the change myself and it worked fine, but I can't karma my own update. Thanks!
*** Bug 1945423 has been marked as a duplicate of this bug. ***
FEDORA-2021-89f1fdaefd has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.