On Mon, Aug 10, 2026, at 11:51 AM, Antonin Kral wrote: > Subject: libqpdf30: CUPS unable to print due to undefined symbol in libqpdf > Package: libqpdf30 > Version: 12.4.0-1 > Severity: important
I wonder if this needs a higher severity than important or whether it just needs a rebuild of cups. > > CUPS stopped working after update. Downgrading to 12.3.2-1+b1 solves the > issue. Relevant message in the CUPS log seems to be: > > D [10/Aug/2026:17:36:35 +0200] [Job 2761] samsung: symbol lookup error: > samsung: undefined symbol: > _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm, > version LIBQPDF_30 That's just std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>>::_M_replace(unsigned long, unsigned long, char const*, unsigned long), which is basically std::string::replace. Oh, wait -- that particular variant of std::string::replace was added in C++-20, which qpdf now uses internally. Could it be that cups is linking with too old of a C++ library? Why would that be? I'm think we just need a rebuild of cups. Maybe that happens automatically because of the binary dependency. > > -- System Information: > Debian Release: forky/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 7.1.5+deb14-amd64 (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_USER, TAINT_WARN > 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 libqpdf30 depends on: > ii libc6 2.42-17 > ii libgcc-s1 16.2.0-1 > ii libgnutls30t64 3.8.13-1 > ii libjpeg62-turbo 1:3.1.3-4 > ii libstdc++6 16.2.0-1 > ii zlib1g 1:1.3.dfsg+really1.3.2-3 > > libqpdf30 recommends no packages. > > libqpdf30 suggests no packages. > > -- no debconf information >
