Unable to launch HandBrake. Used HandBrakeCLI and got the following: "error while loading shared libraries: libvpx.so.11: cannot open shared object file: No such file or directory"
Search Criteria
Package Details: handbrake-full 1.11.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/handbrake-full.git (read-only, click to copy) |
|---|---|
| Package Base: | handbrake-full |
| Description: | Multithreaded video transcoder |
| Upstream URL: | https://handbrake.fr/ |
| Licenses: | LicenseRef-Unredistributable |
| Conflicts: | handbrake |
| Provides: | handbrake |
| Submitter: | FabioLolix |
| Maintainer: | FabioLolix |
| Last Packager: | FabioLolix |
| Votes: | 23 |
| Popularity: | 0.041682 |
| First Submitted: | 2020-08-18 04:32 (UTC) |
| Last Updated: | 2026-03-30 22:00 (UTC) |
Dependencies (59)
- bzip2 (bzip2-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- gdk-pixbuf2 (gdk-pixbuf2-gitAUR, gdk-pixbuf2-noglycinAUR)
- glib2 (glib2-gitAUR, glib2-patched-thumbnailerAUR)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- gst-plugins-base (gst-plugins-base-gitAUR)
- gtk4 (gtk4-paper-planeAUR, gtk4-gitAUR, gtk4-develAUR)
- jansson (jansson-gitAUR)
- lame (lame-svnAUR, lame-altivecAUR)
- libass (libass-gitAUR)
- libdrm (libdrm-gitAUR)
- libjpeg-turbo (mozjpeg-gitAUR, mozjpegAUR, libjpeg-turbo-gitAUR)
- libtheora (libtheora-gitAUR)
- libva (libva-gitAUR, intel-media-stack-legacy-binAUR, intel-media-stack-binAUR, libva-headlessAUR)
- libvorbis (libvorbis-aotuvAUR, libvorbis-aotuv-lancerAUR, libvorbis-gitAUR)
- libvpx (libvpx-full-gitAUR, libvpx-gitAUR)
- libx264.so (x264-tmod-gitAUR, x264-gitAUR, lib32-x264AUR, x264)
- libxml2 (libxml2-gitAUR, libxml2-meson-gitAUR)
- numactl (numactl-gitAUR)
- opus (opus-gitAUR)
- Show 39 more dependencies...
Required by (0)
Sources (1)
darthmongo commented on 2026-03-27 17:45 (UTC)
FabioLolix commented on 2025-10-05 22:22 (UTC)
So it binds to whatever version is present at build time?
Yes, like do a number of Arch packages
Is there any way to avoid this issue?
Maintain your own pkgbuild locally without libx264.so; after the libx264.so soname bump the program will not run
Some users might choose to ignore the x264 upgrade when they see it, which isn't a good idea.
Partial upgrades are unsupported also new packages linked against the new version will fail to run with the old version installed
43615 commented on 2025-10-05 21:30 (UTC)
Alright, I was able to rebuild it. So it binds to whatever version is present at build time? Is there any way to avoid this issue? Some users might choose to ignore the x264 upgrade when they see it, which isn't a good idea.
FabioLolix commented on 2025-10-05 19:23 (UTC)
@43615
since it doesn't specify a version range in the PKGBUILD.
It does by using libx264.so, see the updated pinned comment, otherwise it will fail to run with the error: error while loading shared libraries: libXXX.so.XXX: cannot open shared object file: No such file or directory
43615 commented on 2025-10-05 15:26 (UTC)
This is currently preventing an upgrade:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing x264 (3:0.165.r3222.b35605a-2.4) breaks dependency 'libx264.so=164-64' required by handbrake-full
I don't understand what's going on here, since it doesn't specify a version range in the PKGBUILD.
FabioLolix commented on 2025-08-10 21:05 (UTC) (edited on 2025-10-05 19:21 (UTC) by FabioLolix)
This pkgbuild is maintained at: https://github.com/FabioLolix/PKGBUILD
When you get the error:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing x264 ($VERSION) breaks dependency 'libx264.so=$VERSION' required by handbrake-full
You need to uninstall the package, delete the old version if still around and rebuild the package (reinstalling the previous package will not work)
FabioLolix commented on 2025-05-19 15:18 (UTC)
@carlosnewmusic from your build error:
error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.
The problem is with your rustup configuration, btw building with devtools will never get this error
carlosnewmusic commented on 2025-05-19 14:53 (UTC)
build error https://pastebin.com/XUg2mf0z
43615 commented on 2025-04-26 02:11 (UTC) (edited on 2025-04-26 02:13 (UTC) by 43615)
Same CMake version error, where can I add the flag to this PKGBUILD?
FabioLolix commented on 2025-04-09 10:47 (UTC)
Hi, It Is a common issue with cmake 4, Need thie fix https://aur.archlinux.org/cgit/aur.git/commit/?h=fuzzylite&id=c2f22b0e1a5b099bf5765f26bdd7b037797b244d
Pinned Comments
FabioLolix commented on 2025-08-10 21:05 (UTC) (edited on 2025-10-05 19:21 (UTC) by FabioLolix)
This pkgbuild is maintained at: https://github.com/FabioLolix/PKGBUILD
When you get the error:
You need to uninstall the package, delete the old version if still around and rebuild the package (reinstalling the previous package will not work)