You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Launching Orca starts the GNOME Orca screen reader on Ubuntu (CLI installs as orca, colliding with /usr/bin/orca) #7904
Short summary:
On Ubuntu GNOME, launching Orca (or its MCP integration) starts the GNOME Orca screen reader, which begins speaking out loud. The shell command is installed as orca by default — the same name on every platform — but on stock Ubuntu /usr/bin/orca is the GNOME screen reader, so orca ... invocations can resolve to the screen reader instead of the IDE CLI.
What happened?
On my install the CLI registered as orca (the cross-platform default). Every time the IDE launched and started using the orca MCP, the GNOME screen reader started up and began reading the screen aloud. Nothing in the IDE indicated why — it looked like the OS randomly enabling accessibility.
Notably, the Electron executable itself was already renamed to orca-ide on Linux to avoid exactly this (the launcher script comments say "Linux executableName is orca-ide (avoids Ubuntu GNOME Orca conflict)"), but the shell command / MCP invocation still uses the bare name orca, so the collision remains.
How can we reproduce it?
Ubuntu 26.04 GNOME with the default orca screen reader package installed (it ships with the desktop).
Install Orca IDE from the .deb and install the shell command — it registers as orca.
Launch Orca and let it start the orca MCP.
The GNOME screen reader starts and begins speaking.
Anything else that might help:
My temporary workarounds, in case they help others:
renamed the installed orca command to orca-ide so it stops hitting the screen reader;
uninstalled the orca screen reader package entirely;
re-added ~/.local/bin/orca -> /opt/Orca/resources/bin/orca-ide so orca resolves to the IDE CLI (~/.local/bin precedes /usr/bin on Ubuntu).
Suggested fix: on Linux, install the shell command as orca-ide (matching the executable) and only add an orca alias when nothing named orca already exists on PATH; and/or have the IDE invoke its own CLI by absolute path (/opt/Orca/resources/bin/orca-ide) instead of a bare orca PATH lookup, so the MCP can never accidentally spawn the screen reader.
Activity
ArtuArtaza commentedon Jul 12, 2026
Thank you buddy. I was driving crazy with this issue. I hope this get fixed soon.
fix(linux): stop Orca terminals from launching the GNOME Orca screen …
fix(orchestration): let a structured worker actually reach the Orca C…
feat(orchestration): orchestrate native-born structured chat sessions (…
fix(orca): resolve Orca's CLI instead of trusting bare orca
fix(linux): stop Orca terminals from launching the GNOME Orca screen …
feat(orchestration): orchestrate native-born structured chat sessions (…