Debian Package Tracker
Register | Log in
Subscribe

poppler

Choose email to subscribe with

general
  • source: poppler (main)
  • version: 25.03.0-10
  • maintainer: Debian freedesktop.org maintainers (archive) (DMD)
  • uploaders: Loic Minier [DMD] – Emilio Pozuelo Monfort [DMD] – Pino Toscano [DMD]
  • arch: all any
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 20.09.0-3.1+deb11u1
  • o-o-sec: 20.09.0-3.1+deb11u2
  • oldstable: 22.12.0-2+deb12u1
  • stable: 25.03.0-5
  • testing: 25.03.0-10
  • unstable: 25.03.0-10
versioned links
  • 20.09.0-3.1+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 20.09.0-3.1+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 22.12.0-2+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 25.03.0-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 25.03.0-10: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 25.03.0-11: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • gir1.2-poppler-0.18
  • libpoppler-cpp-dev
  • libpoppler-cpp2
  • libpoppler-dev
  • libpoppler-glib-dev
  • libpoppler-glib-doc
  • libpoppler-glib8t64
  • libpoppler-private-dev
  • libpoppler-qt5-1t64
  • libpoppler-qt5-dev
  • libpoppler-qt6-3t64
  • libpoppler-qt6-dev
  • libpoppler147
  • poppler-utils (50 bugs: 0, 29, 21, 0)
action needed
A new upstream version is available: 25.10.0 high
A new upstream version 25.10.0 is available, you should consider packaging it.
Created: 2025-10-03 Last update: 2025-10-11 14:30
4 security issues in trixie high

There are 4 open security issues in trixie.

1 important issue:
  • CVE-2025-52885: Poppler ia a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector `stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.
1 issue left for the package maintainer to handle:
  • CVE-2025-43718: (needs triaging) Poppler 24.06.1 through 25.x before 25.04.0 allows stack consumption and a SIGSEGV via deeply nested structures within the metadata (such as GTS_PDFEVersion) of a PDF document, e.g., a regular expression for a long pdfsubver string. This occurs in Dict::lookup, Catalog::getMetadata, and associated functions in PDFDoc, with deep recursion in the regex executor (std::__detail::_Executor).

You can find information about how to handle this issue in the security team's documentation.

2 ignored issues:
  • CVE-2019-9543: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readGenericBitmap() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfseparate binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JArithmeticDecoder::decodeBit.
  • CVE-2019-9545: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readTextRegion() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfimages binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JBIG2Bitmap::clearToZero.
1 issue that should be fixed with the next stable update:
  • CVE-2025-50420: An issue in the pdfseparate utility of freedesktop poppler v25.04.0 allows attackers to cause an infinite recursion via supplying a crafted PDF file. This can lead to a Denial of Service (DoS).
Created: 2025-08-04 Last update: 2025-10-11 12:00
3 security issues in sid high

There are 3 open security issues in sid.

3 important issues:
  • CVE-2019-9543: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readGenericBitmap() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfseparate binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JArithmeticDecoder::decodeBit.
  • CVE-2019-9545: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readTextRegion() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfimages binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JBIG2Bitmap::clearToZero.
  • CVE-2025-52885: Poppler ia a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector `stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.
Created: 2022-07-04 Last update: 2025-10-11 12:00
3 security issues in forky high

There are 3 open security issues in forky.

3 important issues:
  • CVE-2019-9543: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readGenericBitmap() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfseparate binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JArithmeticDecoder::decodeBit.
  • CVE-2019-9545: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readTextRegion() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfimages binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JBIG2Bitmap::clearToZero.
  • CVE-2025-52885: Poppler ia a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector `stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.
Created: 2025-08-09 Last update: 2025-10-11 12:00
7 security issues in bookworm high

There are 7 open security issues in bookworm.

1 important issue:
  • CVE-2025-52885: Poppler ia a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector `stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.
4 issues left for the package maintainer to handle:
  • CVE-2025-43718: (needs triaging) Poppler 24.06.1 through 25.x before 25.04.0 allows stack consumption and a SIGSEGV via deeply nested structures within the metadata (such as GTS_PDFEVersion) of a PDF document, e.g., a regular expression for a long pdfsubver string. This occurs in Dict::lookup, Catalog::getMetadata, and associated functions in PDFDoc, with deep recursion in the regex executor (std::__detail::_Executor).
  • CVE-2025-43903: (needs triaging) NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-50420: (needs triaging) An issue in the pdfseparate utility of freedesktop poppler v25.04.0 allows attackers to cause an infinite recursion via supplying a crafted PDF file. This can lead to a Denial of Service (DoS).
  • CVE-2025-52886: (needs triaging) Poppler is a PDF rendering library. Versions prior to 25.06.0 use `std::atomic_int` for reference counting. Because `std::atomic_int` is only 32 bits, it is possible to overflow the reference count and trigger a use-after-free. Version 25.06.0 patches the issue.

You can find information about how to handle these issues in the security team's documentation.

2 ignored issues:
  • CVE-2019-9543: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readGenericBitmap() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfseparate binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JArithmeticDecoder::decodeBit.
  • CVE-2019-9545: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readTextRegion() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfimages binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JBIG2Bitmap::clearToZero.
Created: 2023-06-10 Last update: 2025-10-11 12:00
7 security issues in bullseye high

There are 7 open security issues in bullseye.

1 important issue:
  • CVE-2025-52885: Poppler ia a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector `stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.
4 issues postponed or untriaged:
  • CVE-2025-43718: (postponed; to be fixed through a stable update) Poppler 24.06.1 through 25.x before 25.04.0 allows stack consumption and a SIGSEGV via deeply nested structures within the metadata (such as GTS_PDFEVersion) of a PDF document, e.g., a regular expression for a long pdfsubver string. This occurs in Dict::lookup, Catalog::getMetadata, and associated functions in PDFDoc, with deep recursion in the regex executor (std::__detail::_Executor).
  • CVE-2025-43903: (postponed; to be fixed through a stable update) NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-50420: (postponed; to be fixed through a stable update) An issue in the pdfseparate utility of freedesktop poppler v25.04.0 allows attackers to cause an infinite recursion via supplying a crafted PDF file. This can lead to a Denial of Service (DoS).
  • CVE-2025-52886: (postponed; to be fixed through a stable update) Poppler is a PDF rendering library. Versions prior to 25.06.0 use `std::atomic_int` for reference counting. Because `std::atomic_int` is only 32 bits, it is possible to overflow the reference count and trigger a use-after-free. Version 25.06.0 patches the issue.
2 ignored issues:
  • CVE-2019-9543: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readGenericBitmap() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfseparate binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JArithmeticDecoder::decodeBit.
  • CVE-2019-9545: An issue was discovered in Poppler 0.74.0. A recursive function call, in JBIG2Stream::readTextRegion() located in JBIG2Stream.cc, can be triggered by sending a crafted pdf file to (for example) the pdfimages binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact. This is related to JBIG2Bitmap::clearToZero.
Created: 2025-10-11 Last update: 2025-10-11 12:00
lintian reports 8 errors and 5 warnings high
Lintian reports 8 errors and 5 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2025-09-05 Last update: 2025-10-03 16:25
7 bugs tagged patch in the BTS normal
The BTS contains patches fixing 7 bugs (8 if counting merged bugs), consider including or untagging them.
Created: 2025-01-06 Last update: 2025-10-11 17:28
debian/patches: 6 patches to forward upstream low

Among the 6 debian patches available in version 25.03.0-10 of the package, we noticed the following issues:

  • 6 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2025-04-08 Last update: 2025-10-03 10:32
testing migrations
  • This package will soon be part of the auto-gpgme1.0 transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migration status for poppler (25.03.0-10 to 25.03.0-11): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/poppler.html
    • ∙ ∙ autopkgtest for auto-multiple-choice/1.7.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for bibtexconv/2.0.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for bookletimposer/0.3.1-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for calibre/8.12.0+ds+~0.10.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for camelot-py/0.11.0-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for camlpdf/2.8.1-1: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for cnvkit/0.9.12-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for cups/2.4.14-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for dhelp/0.6.32: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for dia/0.98+git20250827-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for diff-pdf-wx/0.5.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for diffoscope/306: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for doc-rfc/20230121-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for dxf2gcode/20240509-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for evince/48.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for fbi/2.14-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for fig2dev/1:3.2.9a-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for forensics-extra/2.59: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for gdcm/3.0.24-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for gegl/1:0.4.62-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for gimp/3.0.4-6.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered
    • ∙ ∙ autopkgtest for gle-graphics/4.3.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for gsequencer/7.7.5-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for img2pdf/0.6.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for kf6-kfilemetadata/6.18.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for kfilemetadata-kf5/5.116.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for latex2html/2025+debian1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for libcupsfilters/2.0.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for libextractor/1:1.13-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for liblouisxml/2.4.0-15: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for libreoffice: amd64: Test triggered, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ autopkgtest for mat2/0.13.5-1.2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ autopkgtest for origami-pdf/2.1.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for papers/49.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for paperwork/2.2.5-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for plastex/3.1-4: amd64: Test triggered, arm64: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ autopkgtest for poppler/25.03.0-11: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for pycirkuit/0.5.1-3.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for pympress/1.8.5-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for python-poppler-qt5/21.3.0-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for r-cran-pdftools/3.5.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for r-cran-statcheck/1.5.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for ruby-gnome/4.2.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for rust-poppler-sys-rs/0.25.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for tcpdf/6.9.1+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for texworks/0.6.10+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for xapers/0.9.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Waiting for lintian test results (stalls migration) - info
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info:
    • ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻
    • ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
    • Not considered
news
[rss feed]
  • [2025-10-11] Accepted poppler 25.03.0-11 (source) into unstable (Pino Toscano)
  • [2025-10-05] poppler 25.03.0-10 MIGRATED to testing (Debian testing watch)
  • [2025-10-02] Accepted poppler 25.03.0-10 (source) into unstable (Jeremy Bícha)
  • [2025-09-11] poppler 25.03.0-9 MIGRATED to testing (Debian testing watch)
  • [2025-09-05] Accepted poppler 25.03.0-9 (source) into unstable (Jeremy Bícha)
  • [2025-09-03] poppler 25.03.0-7 MIGRATED to testing (Debian testing watch)
  • [2025-09-01] poppler 25.03.0-6 MIGRATED to testing (Debian testing watch)
  • [2025-08-31] Accepted poppler 25.03.0-7 (source) into unstable (Jeremy Bícha)
  • [2025-08-27] Accepted poppler 25.03.0-6 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-07-30] poppler 25.03.0-5 MIGRATED to testing (Debian testing watch)
  • [2025-07-28] Accepted poppler 25.03.0-5 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-05-10] Accepted poppler 22.12.0-2+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Adrian Bunk)
  • [2025-04-28] Accepted poppler 20.09.0-3.1+deb11u2 (source) into oldstable-security (Adrian Bunk)
  • [2025-04-24] poppler 25.03.0-4 MIGRATED to testing (Debian testing watch)
  • [2025-04-18] Accepted poppler 25.03.0-4 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-04-10] poppler 25.03.0-3 MIGRATED to testing (Debian testing watch)
  • [2025-04-07] Accepted poppler 25.03.0-3 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-03-14] poppler 25.03.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-03-06] Accepted poppler 25.03.0-2 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-03-05] Accepted poppler 25.03.0-1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Jeremy Bicha)
  • [2025-03-02] poppler 25.01.0-5 MIGRATED to testing (Debian testing watch)
  • [2025-02-27] Accepted poppler 25.01.0-5 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-02-13] poppler 25.01.0-4 MIGRATED to testing (Debian testing watch)
  • [2025-02-07] Accepted poppler 25.01.0-4 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-02-03] Accepted poppler 25.01.0-3 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-01-29] poppler 25.01.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-01-26] Accepted poppler 25.01.0-2 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • [2025-01-16] Accepted poppler 25.01.0-1 (source amd64) into experimental (Debian FTP Masters) (signed by: Jeremy Bicha)
  • [2025-01-09] poppler 24.08.0-4 MIGRATED to testing (Debian testing watch)
  • [2025-01-05] Accepted poppler 24.08.0-4 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
  • 1
  • 2
bugs [bug history graph]
  • all: 106 111
  • RC: 0
  • I&N: 75 79
  • M&W: 31 32
  • F&P: 0
  • patch: 7 8
links
  • homepage
  • lintian (8, 5)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • l10n (-, 100)
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 25.03.0-7
  • 99 bugs (5 patches)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing