Your message dated Fri, 10 Jul 2026 16:34:58 +0100
with message-id <[email protected]>
and subject line Re: Bug#1141660: zathura fails to start: undefined symbol
gst_play_config_set_loop
has caused the Debian Bug report #1141660,
regarding zathura fails to start: undefined symbol gst_play_config_set_loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1141660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141660
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zathura
Version: 2026.07.02-3
Severity: important
Dear Maintainer,
zathura in testing and unstable seems to suffer some linking issues, crashing
before startup with message:
zathura: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgtk-4.so.1:
undefined symbol: gst_play_config_set_loop
I tested versions 2026.07.02-1 and 2026.07.02-3 .
This looks to me vaguely similar to a situation with gajim in #1130014 , but I
was unable to fix this by applying the same dependency change. Might be the
case that this is actually a problem of libgtk-4-1, but I found I don't have
other gtk4 apps to bisect.
In case some debug information is needed to solve this, please let me know.
-mk
-- System Information:
Debian Release: forky/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (1,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 7.0.13+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages zathura depends on:
ii libc6 2.42-17
ii libcairo2 1.18.4-3+b1
ii libgirara5 2026.02.04-4
ii libglib2.0-0t64 2.88.2-1
ii libgraphene-1.0-0 1.10.8-5+b2
ii libgtk-4-1 4.22.4+ds-1
ii libjson-glib-1.0-0 1.10.8+ds-2+b1
ii libmagic1t64 1:5.47-4
ii libpango-1.0-0 1.58.0-1
ii libpangocairo-1.0-0 1.58.0-1
ii libseccomp2 2.6.0-2+b1
ii libsqlite3-0 3.46.1-9+b1
ii libsynctex2 2026.20260303.78225+ds-4
ii libxxhash0 0.8.3-2+b2
ii zathura-pdf-poppler 2026.05.10-1+b1
zathura recommends no packages.
Versions of packages zathura suggests:
ii firefox [www-browser] 152.0.5~build1
ii links2 [www-browser] 2.29-2+b4
ii lynx [www-browser] 2.9.3-2
ii surf [www-browser] 2.1+git20250419-1
ii ungoogled-chromium [www-browser] 149.0.7827.196-1mx25
pn zathura-cb <none>
pn zathura-djvu <none>
pn zathura-ps <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 10 Jul 2026 at 16:02:27 +0200, Miroslav Kratochvil wrote:
- this was indeed caused by a stray library, in this case
libgstreamer-plugins-bad1.0 that was soaked in from a different
repository (when trying to find the source of the bug that repository
was already disabled but the package stayed).
Thanks, closing as "not Debian's bug".
If the third-party repository is deb-multimedia.org, then this is the
same root cause as #1130014, or if not, then it's likely to be a very
similar root cause.
smcv
--- End Message ---
