Chromium-browser undefined symbol

After updating to chromium-119.0.6045.199-1.fc38.x86_64, it now will not start:

$ chromium-browser
/usr/bin/chromium-browser: symbol lookup error: /usr/bin/chromium-browser: undefined symbol: av_stream_get_first_dts, version LIBAVFORMAT_60

$ echo $?
127

I do not know why Chromium now wants that or how to satisfy it.

FYI, most of my media software comes from negativo17.org.  Of the below, only libavc1394, libavif and libavtp are from Fedora’s repository:

$ sudo rpm -qa | grep libav | sort
gstreamer1-plugin-libav-1.22.5-1.fc38.x86_64 #
libavc1394-0.5.4-19.fc38.x86_64
libavcodec58-4.4.4-1.fc38.x86_64
libavcodec-6.0.1-1.fc38.x86_64
libavdevice-6.0.1-1.fc38.x86_64
libavfilter-6.0.1-1.fc38.x86_64
libavformat58-4.4.4-1.fc38.x86_64
libavformat-6.0.1-1.fc38.x86_64
libavif-0.11.1-7.fc38.x86_64
libavtp-0.2.0-4.fc38.x86_64
libavutil56-4.4.4-1.fc38.x86_64
libavutil-6.0.1-1.fc38.x86_64

I’ve not removed the negativo17.org RPMs to test; I thought I’d post here, first, to see if anybody else had a suggestion since everything had been working fine prior to the update.

(BTW, seeing libavcodec58 and libavformat58 in that list, I looked for a libav60 RPM and did not find one.)

While I do not, and never have, use negativo17 software, I have seen problems fixed by removing everything installed from there and instead use plain vanilla fedora with the added rpmfusion multimedia packages.

Fedora’s chromium package was changed to use system ffmpeg, and Fedora’s ffmpeg now carries a patch to add that symbol for chromium. RPM Fusion also added it to their package (reluctantly).

Thank you, @computersavvy and @chrisawi for the education in how multimedia codecs should be installed and in what happened behind the scenes to cause this problem. Your insights are appreciated!