Bug 1952559 - Orca not working with web browsers.
Summary: Orca not working with web browsers.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: orca
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-22 14:44 UTC by bez.powell
Modified: 2021-04-28 13:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-28 13:11:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bez.powell 2021-04-22 14:44:16 UTC
Description of problem:
Orca does not work for me with web browsers. When opening a web browser it stops speaking out elements and none of the hotkeys work.

I have tested on Firefox, Chromium, and Tor Browser. Neither Firefox or Chromium work, regardless of whether they or Orca are started first. Tor browser, however, does sometimes work if Orca is running before it is started. In this case, Orca works with tor browser as expected.

Version-Release number of selected component (if applicable):
orca-3.38.2-1.fc33.noarch
firefox-88.0-1.fc33.x86_64
chromium-89.0.4389.90-3.fc33.x86_64

How reproducible:
All the time for Firefox and Chrome. Most of the time for tor browser.

Steps to Reproduce:
1. Start Orca as usual. Try hotkeys and reading out elements in gnome.
2. Start up a browser. Try hotkeys.

Actual results:
Orca goes silent as soon as a browser is opened. No orca hotkeys work as long as the browser has focus.

Expected results:
Orca starts reading out browser and hotkeys remain functional.

Additional info:
This system has been upgraded through a few versions of Fedora and thus is not a totally clean install. All of the packages are from the official Fedora repositories.

Comment 1 Kalev Lember 2021-04-22 14:55:33 UTC
Sorry, I don't think I can help with this, but maybe you could file a ticket upstream at https://gitlab.gnome.org/GNOME/orca to see if the upstream developers have any ideas?

Comment 2 bez.powell 2021-04-22 15:06:10 UTC
(In reply to Kalev Lember from comment #1)
> Sorry, I don't think I can help with this, but maybe you could file a ticket
> upstream at https://gitlab.gnome.org/GNOME/orca to see if the upstream
> developers have any ideas?

I'll try that now, thank you. I initially filed here as someone else reported that it was working okay for them on Ubuntu, so assumed it might be a Fedora specific problem.

Comment 3 Kalev Lember 2021-04-23 10:29:09 UTC
No problem! The difference is probably because Ubuntu uses X11 session by default and Fedora uses Wayland. You could maybe try to work this around by choosing the X11 session at the login screen.

Comment 4 bez.powell 2021-04-23 13:22:12 UTC
Hi Kalev,

I actually am using X11, as my system has a nVidia GPU (I should have known better, but was won over by a large discount when purchasing). I have heard that there can be some problems when using Orca on Wayland, is that likely to be an issue if I ever switch over to using an AMD GPU and thus Wayland?

Comment 5 Kalev Lember 2021-04-23 14:49:47 UTC
I have heard so as well. But you should be able to just keep on using X11 in that case.

Comment 6 bez.powell 2021-04-28 10:10:50 UTC
I've just performed a complete re-install to 34, and the screen reader is working as expected now. I suspect there may have been some mis-configuration on my end that caused it to break.

Comment 7 Kalev Lember 2021-04-28 13:11:25 UTC
Oh, that's good to hear. Thanks for letting me know! I think we can close the ticket then.


Note You need to log in before you can comment on or make changes to this bug.