Could you do ldd on the affected binaries? This looks like your local system problem. Can you reproduce this on clean Debian system?
Thanks, -- Ondřej Surý (He/Him) [email protected] > On 8. 1. 2025, at 12:26, Bertrand Belguise <[email protected]> wrote: > > Package: bind9-dnsutils > Version: 1:9.20.4-3 > Severity: important > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > when using dig, host, nslookup get the error : > symbol lookup error: /lib/x86_64-linux-gnu/libisc-9.20.4-3-Debian.so: > undefined symbol: mallocx > > Same problem with experimental version > > > -- System Information: > Debian Release: trixie/sid > APT prefers testing > APT policy: (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.12.6-amd64 (SMP w/2 CPU threads; PREEMPT) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages bind9-dnsutils depends on: > ii bind9-host [host] 1:9.20.4-3 > ii bind9-libs 1:9.20.4-3 > ii libc6 2.40-4 > ii libedit2 3.1-20240808-1 > ii libidn2-0 2.3.7-2+b1 > ii libjemalloc2 5.3.0-2+b2 > ii libkrb5-3 1.21.3-3 > ii libprotobuf-c1 1.4.1-1+b3 > > bind9-dnsutils recommends no packages. > > bind9-dnsutils suggests no packages. > > -- no debconf information >
