Alex wrote:
After upgrading to gajim 2.4.4-1, it does not start anymore. It shows
the warning
Failed to load shared library 'libgtk-4.so.1' referenced by the typelib:
/usr/lib/x86_64-linux-gnu/libgtk-4.so.1: undefined symbol:
gst_play_config_set_loop
and afterward crashes at a python assert related to gi
...
ii gstreamer1.0-plugins-bad 1:1.26.0-dmo1+b1
This is a recurring problem: this version of gstreamer1.0-plugins-bad
from deb-multimedia.org is known to break Debian's GTK 4 package. I
would recommend avoiding the use of any packages from
deb-multimedia.org, particularly if you are using testing/unstable.
Debian's GTK 4 requires a quite recent version of
libgstreamer-plugins-bad1.0-0 (currently 1.28.3 or later), and has a
correct versioned dependency on that version.
deb-multimedia.org's packaging of gst-plugins-bad1.0 is only version
1.26.0, but it has been versioned with an epoch (notice the 1: prefix)
which instructs apt to behave as though it was newer than any version
without an epoch. This results in apt installing GTK 4 with a too-old
version of libgstreamer-plugins-bad1.0-0, and the result is that GTK's
requirements are not met, even though apt thinks they are.
This problem can be avoided by installing Debian's official
libgstreamer-plugins-bad1.0-0 package: apt will behave as though this is
a downgrade (because of the epoch) but it's actually an upgrade. And,
more generally, I would suggest replacing any packages from
deb-multimedia.org ("dpkg-query -W | grep -e -dmo" would be a good starting
point) with their official Debian equivalents.
Martin wrote:
* Promote Recommends of gstreamer1.0-plugins-bad to versioned Depends
(Closes: #1130014)
Unfortunately, this is probably not going to solve the problem, because
deb-multimedia.org's gstreamer1.0-plugins-bad package is likely to have
the same incorrect version information as its
libgstreamer-plugins-bad1.0-0 package.
smcv
