Skip to content

Possible collision with another orca executable #1299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MFolschette opened this issue Dec 11, 2018 · 0 comments · Fixed by #1519
Closed

Possible collision with another orca executable #1299

MFolschette opened this issue Dec 11, 2018 · 0 comments · Fixed by #1519

Comments

@MFolschette
Copy link

When using Plotly-Orca with Ubuntu 18.04, and while following the installation instructions, I met a problem that is not mentioned in the help: There already exists another binary named orca that is pre-installed on some Ubuntu systems (it is a screen reader that is not related to this Orca). This problem arose because the folder of Miniconda executables is at the end of my PATH environment variable, thus the /usr/bin/orca is found first.

The problem was solved after I addressed it on the Plotly forums.

I would recommend tackling this in the README.md in the Installation section or a Troubleshooting section:

##Troubleshooting: wrong executable found
If you meet issues with the orca executable not being the correct one, this may be due to another executable with the same name existing on your system. Please specify the complete path to the Plotly-Orca binary that you downloaded (for instance in the Miniconda folder) with the following command:
plotly.io.orca.config.executable = '/home/your_name/miniconda3/bin/orca'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants