-
Notifications
You must be signed in to change notification settings - Fork 369
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
[0.18 RC1 - 64-bit build]: OSError: libmmal.so: cannot open shared object file: No such file or directory #702
Comments
This issue may be the duplicate of #697 |
Also related to #700 |
Now also related to #711 |
The now Ubuntu 64bit builds might solve this. I am not sure |
Did you solve it? having the same issue :( |
@kaczmaro Please provide the image you are using. There is a nightly build that might solve it. |
I'm using Raspberry Pi OS Lite (64-bit) Release date: September 22nd 2022, and python3-picamera/stable,now 1.13 arm64, and got the same error While, I found a PiCamera2, and it seems able to import. I'm still trying how to use it. It PiCamera2 relative with PiCamera? |
What were you doing?
I'm the author of The Spaghetti Detective and OctoPrint Anywhere plugins. Users of both plugins have run into the same issues when they are using 0.18 RC1.
Here are the minimum number of steps to reproduce the issue:
sudo apt upgrade
.source ~/oprint/bin/activate
pip install picamera
python -c "import picamera"
What did you expect to happen?
The command runs successfully with no output.
What happened instead?
The command outputs:
Did the same happen when running OctoPrint in safe mode?
N/A
Version of OctoPi
0.18 RC1. Please note this bug only happens in the 64-bit build. The 32-bit build is good.
Printer model & used firmware incl. version
N/A
Screenshot(s)/video(s) showing the problem:
N/A
For a bit more info:
libmmal.so
is the driver for Pi Camera. On older versions of OctoPi, as well as the 32-bit build of 0.18 RC1, it is located in/opt/vc/lib
. However, the entire folder is missing from the 64-bit build of 0.18 RC1.The text was updated successfully, but these errors were encountered: