Your message dated Fri, 19 Dec 2025 11:56:10 +0100 with message-id <176614177081.2665700.2414343561355429011@cairon.jones.dk> and subject line Re: unpaper: undefined symbol: vaSyncBuffer has caused the Debian Bug report #1035022, regarding unpaper: undefined symbol: vaSyncBuffer 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 owner@bugs.debian.org immediately.) -- 1035022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035022 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: unpaper: undefined symbol: vaSyncBuffer
- From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
- Date: Thu, 27 Apr 2023 13:30:06 -0400
- Message-id: <CAPQV63VCVJuZNyaVOmNbQHcANF+oDeYHu4j4OM0f0k9qg3GA0g@mail.gmail.com>
Package: unpaper
Version: 7.0.0-0.1
Severity: important
Dear Maintainer,
* What led up to the situation?
Launching the application from command line gives an error. Unable to start it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Simply entered "unpaper" in the command line.
* What was the outcome of this action?
The following error message:
unpaper: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer
* What outcome did you expect instead?
Anything but what I got. As an example, the version being printed in the output.
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages unpaper depends on:
ii libavcodec59 10:5.1.3-dmo3
ii libavformat59 10:5.1.3-dmo3
ii libavutil57 10:5.1.3-dmo3
ii libc6 2.36-9
unpaper recommends no packages.
unpaper suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 1035022-done@bugs.debian.org
- Subject: Re: unpaper: undefined symbol: vaSyncBuffer
- From: Jonas Smedegaard <dr@jones.dk>
- Date: Fri, 19 Dec 2025 11:56:10 +0100
- Message-id: <176614177081.2665700.2414343561355429011@cairon.jones.dk>
- Reply-to: 1035022@bugs.debian.org
Hi Jean-Marc, I just stumbled upon a bugreport that you filed a few years ago. First of all, sorry that we didn't manage to get back to you sooner. Reason for that is that the packaging of the unpaper project has had no dedicated maintainer for some time: https://bugs.debian.org/1019012 I sure hope you have solved your problem long ago, but if not, and for posterity, see further comments below the quote... > Launching the application from command line gives an error. > Unable to start it. [...] > The following error message: > unpaper: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: > undefined symbol: vaSyncBuffer [...] > Versions of packages unpaper depends on: > ii libavcodec59 10:5.1.3-dmo3 > ii libavformat59 10:5.1.3-dmo3 > ii libavutil57 10:5.1.3-dmo3 > ii libc6 2.36-9 The issue seems to be caused by the inclusion of non-Debian libraries, which I guess were, at the time of your reporting the bug, out of sync with Debian. I am only guessing, and Debian has given up many years ago to try help users that choose to mix Debian with other sources. More information specifically about what might be mixed in here is at https://wiki.debian.org/DebianMultimedia/FAQ#Common_issues More information more generally about Debian discouraging mixing of multiple sources is at https://wiki.debian.org/DontBreakDebian All that said, you are of course free to use Debian however you want, including in ways that we do not recommend or are able to support. Kudos for using debbugs and preserving its autogenerated dependency list, aiding in quickly identifying this as a case of "FrankenDebian". Hereby closing this as a non-Bug (in Debian, specifically). All the best to you, regardless if you are still a Debian user, or have moved on to explore other options, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep privateAttachment: signature.asc
Description: signature
--- End Message ---