Minidlna not working on snapshot build

running the master branch on bananapi r2 since two years
Suddenly the minidlna service stops. As I see, the update to ffmpeg 5 is the reason.

Mar 20 18:33:48 bananapi minidlnad[1976]: Error loading shared library libavformat.so.58: No such file or directory (needed by /usr/sbin/minidlnad)
Mar 20 18:33:48 bananapi minidlnad[1976]: Error loading shared library libavcodec.so.58: No such file or directory (needed by /usr/sbin/minidlnad)
Mar 20 18:33:48 bananapi minidlnad[1976]: Error loading shared library libavutil.so.56: No such file or directory (needed by /usr/sbin/minidlnad)
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: av_strerror: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: av_log_set_level: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: av_reduce: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: avformat_close_input: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: avformat_find_stream_info: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: av_dict_get: symbol not found
Mar 20 18:33:49 bananapi minidlnad[1976]: Error relocating /usr/sbin/minidlnad: avformat_open_input: symbol not found

The issue is descibed here: https://github.com/openwrt/packages/issues/18011

How can I solve the problem? I thought, because I compile my image by my own, the issue had to be solved by self. Big mistake...

Workaround:
I manually created links to the new files

cd /usr/lib
ln -s libavutil.so.57.17.100 libavutil.so.56
ln -s libavformat.so.59.16.100 libavformat.so.58
ln -s libavcodec.so.59.18.100 libavcodec.so.58

afterwards I restarted the minidlnad service without marks in the systemlog. Luci says, minidlna will serve 1800 files.

1 Like

Not half the solution. Works only for music files, but pics and video files are not recognized.

no reaction anywhere (neither here or at github) and the bug still remains also in build 19657. Hope, the maintainers will fix this until 22.03 will released.