I’m trying to set up the Arducam High Resolution Autofocus Camera Module on my Raspberry Pi 4B that already has OctoPrint on it. I’ve been following the native camera quick start guide at Quick Start Guide - Arducam Wiki and I got stuck at step 5 where it covers libcamera-apps. When I run libcamera-still it just dies with:
libcamera-still: error while loading shared libraries: libepoxy.so.0: cannot open shared object file: No such file or directory
The camera seemed to be detected earlier, but this step won’t run at all. Any ideas what I’m missing?
That error means the libepoxy.so.0 shared library isn’t installed on the system, and libcamera-still needs it at runtime to link. Try installing the package that provides it:
sudo apt install libepoxy0
After that finishes, run libcamera-still again and see if it gets further. If it errors out on a different .so file, don’t worry too much — that would just be a different missing library and we can handle it the same way.
Right, that means the device is missing more than one shared library, not just libepoxy. Install the Qt5 core package now:
sudo apt install libQt5Core5
Then try libcamera-still -t 5000 again. If it throws another ‘cannot open shared object file’ for a different .so file, just install the matching package for that library and keep going. These are usually just missing runtime dependencies, so it may take a couple of rounds before everything it needs is present.
That chmod error is a bit different from the library issues. The way it’s printed, with the whole line shown, usually means bash tried to run the entire string as a single command name instead of running chmod with arguments. So first double-check there’s a real space between chmod and +x, and that you didn’t accidentally paste any stray characters (like smart quotes or a non-breaking space).
You can also verify the chmod binary itself is fine by running:
which chmod
/bin/chmod --version
If /bin/chmod works directly, then the problem is with how the command line was entered. If both fail, then something is off with the system PATH or the coreutils install.
To summarize where we are: the original libcamera-still failures were missing shared libraries (libepoxy.so.0 and libQt5Core.so.5), which are handled by installing the matching packages as they appear. The current blocker on the fresh install is that chmod isn’t being executed at all, which looks like a command-entry/PATH problem rather than a camera issue. Try retyping the chmod line manually (not pasting it) and let us know what ‘which chmod’ returns.