-
Notifications
You must be signed in to change notification settings - Fork 162
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
ImportError: libcoppeliaSim.so.1: cannot open shared object file: No such file or directory #98
Comments
Hi, |
yes,of course |
i have try the python3.7 and reorder the LD_LIBRARY_PATH setting. but it dosen't work. |
Hmm, I'm not sure. Have you followed the updated readme in #93? |
Same here, I'm not using conda either |
Are you able to run CoppeliaSim as normal (without Python)? |
Yes |
I see the problem in the case of the last screenshot posted by @XuankeShi. You were running under python(2) rather than python3. Perhaps this is your issue too @raghada? |
No, I'm using python3 |
i hope we can solve this question. my friend and i have the same question. and we don't know wnowhy. |
i use python3 ,the screenshot i post may be a mistake. |
What version of CoppeliaSim are you both using (major/minor/revision number)? |
I'm using V4.0.0 Rev 4 |
I tried reinstalling ubuntu as well as CoppeliaSim, no thing works. |
I have some good news. I was able to reproduce by pulling the latest CoppeliaSim version. I had V4.0.0 Rev 2 locally. I can't fix this right now, but should be able to tomorrow (as long as the fix is a simple as I imagine). For now, I recommend that you use revision 2 rather than revision 4. |
Very much appreciated! |
Coulod you please advice on where to find revision 2? I was not able to find it in their website |
Hi guys remember to |
launch pycharm in terminal probably can solve this problem,because Pycharm could load LD_library_path from bashrc when you launch pycharm in terminal. |
this works for me |
we i run the example
it occurs an ImportError: libcoppeliaSim.so.1: cannot open shared object file: No such file or directory
The text was updated successfully, but these errors were encountered: