Closed PaulKraut closed 4 months ago
As a workaround and specially for Arch Linux:
There is an AUR-Package of ffmpeg6.1 6.1.1-1, that contains the current and fixed version of ffmpeg 6, that delivers libswscale.so.7.5.100. If you build the package, put the binaries to i.e. /opt/lib/ffmpeg6, you can point LD_LIBRARY_PATH to that directory and may start droidcam or any other app, that depends on libswscale.so.7.
Since I assumed, that the package may interfere with the common or other ffmpeg packages, I deployed it to /opt/lib. If someone has a cleaner solution: Any helping hand is welcome :)
Disclaimer: Of course you have either to check the code of the PKGBUILD-file or to trust its author, as I do (since I do not know, what all these git cherry-pickings really do ;-) ) ..
I believe this is an issue with the Arch package. The downloads on the app website are statically linked, and should not break when the system ffmpeg version changes: https://www.dev47apps.com/droidcam/linux/
As a fix you could also just rebuild droidcam, which automatically links against the currently installed libswscale.
I suggest using rebuild-detector after every pacman -Syu
so you can see which AUR package needs to be rebuilt
@HorayNarea That was exactly the issue, thanks for the hints!
Describe the bug After updating Arch Linux / KDE Plasma 6.1 to the latest version, droidcam did not start any more, stating:
Dirty trying to symlink ./libswscale.so.7 -> ./libswscale.so.8 leads to error message
Expected behavior Starting of droidcam with the virtual camera
Additional context