[Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
When pdftocairo ist used with libcairo2-1.15.12-1 -- which (AFAIK) contains the bug I linked above -- to output a pdf file (as pdftopdf 1.21 will do!), it would be no surprise have a corrupt pdf after pdftocairo, which gs then rightly will complain about; esp. the ET -thing is the one things such a buggy libcairo2 will produce. The only thing form-flattening has to do with it, is that pdftopdf 1.21 would only call pdftocairo when a form is present in the pdf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817033 Title: Unable to correctly print PDF file: Error: Ignoring spurious ET operator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1817033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
My observations: As changing pdftops-renderer does not seem to make a difference, probably only one of the programs is installed and thus used in all cases? According to Dependencies.txt, libcairo2-1.15.12-1 seems to installed, which AFAIK is affected by the problem described e.g. here: https://github.com/Kozea/WeasyPrint/issues/705 I have no explanation though, how the pdf (which, by itself, does not seem to contain the error, AFAIAC) would run through the cairo pdf backend ... It does not really seem form-related, but there are some options to change the form-flattening engines (Till?) - or could it possibly be that the 1.21 cups-filter uses some pdf-to-pdf form flattening which uses the cairo backend ? ** Bug watch added: github.com/Kozea/WeasyPrint/issues #705 https://github.com/Kozea/WeasyPrint/issues/705 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817033 Title: Unable to correctly print PDF file: Error: Ignoring spurious ET operator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1817033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670730] Re: pdftopdf "inflate data - incorrect data check" with certain PDFs
Object 39 is an image; but even Object 4 (the content stream of the first page; obj 93 *is* used on that page) has such a decompression error. Ghostscript prints: warning: ignoring zlib error: incorrect data check So probably libqpdf (which is used for the very low-level pdf stuff in pdftopdf) should also handle this as warning instead of as error? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670730 Title: pdftopdf "inflate data - incorrect data check" with certain PDFs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1670730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page
For example, here some java/PDFBox-based implementation of how to flatten simple forms: https://gist.github.com/jribble/beddf7620536939f88db (IIRC there are more form elements than those 2-3 handled here(?)). Note that QPDF does not have something like the PDAcroForm class (and its friends) used there to easily access the form data. So any QPDF/C++ based form flattener has to implement that, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564249 Title: Cannot print a PDF with AcroForms using fit-to-page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1564249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564249] Re: Cannot print a PDF with AcroForms using fit-to-page
See https://bugs.linuxfoundation.org/show_bug.cgi?id=1315 why this cannot work.
And QPDF won't be able to do anything about it, either...
There might even be PDF-capable printers on the market (i.e. where the
rasterization is not done by gs / poppler on the host), where the form content
will not be printed even without the fit-to-page option.
The PDF format generally does not allow arbitrary transformations (as used by
pdftopdf in certain cases) to be applied to the ("interactive") Form content -
which is stored separately from the Page content.
The usual solution for printing is that the viewer application (Evince, Google
Chrome, ...) converts (hard-codes) any Form content into regular Page content
before sending the data to the printing chain. Using lpr skips this
(non-trivial) step.
** Bug watch added: bugs.linuxfoundation.org/ #1315
https://bugs.linuxfoundation.org/show_bug.cgi?id=1315
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564249
Title:
Cannot print a PDF with AcroForms using fit-to-page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1564249/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464783] Re: Number up option is processed before the page extraction option
According to Mike Sweet [1]: Dec 28, 2007 by Michael Sweet: The 1.1.x (and 1.0.x) behavior was incorrect. According to the IPP specification, number-up is applied *first*, and page-ranges refers to the imposed pages. Similarly, page-set is applied after imposition. and here [2]: Nov 16, 2008 by Michael Sweet: IPP specifies the page-ranges applies after imposition, so the current implementation is correct. I'll add a note to the documentation about the behavior. My man page of lp(1) says: -P page-list Specifies which pages to print in the document. The list can contain a list of numbers and ranges (#-#) separated by commas (e.g. 1,3-5,16). The page numbers refer to the output pages and not the document's original pages - options like number-up can affect the numbering of the pages. And -P is just a shortcut for page-ranges=. For that reason pstops handles page-ranges the way it does. And pdftopdf deliberately follows pstops' logic. However I don't know which IPP specification Mike references here. From my understanding of RFC2911 (IPP 1.1), Section 15.3 [3], page-ranges is applied in step 2, and number-up is applied only in the next step 3. Maybe Mike can shed some light on this issue? [1] http://cups.org/str.php?L2643 [2] http://cups.org/str.php?L3008 [3] https://tools.ietf.org/html/rfc2911#section-15.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464783 Title: Number up option is processed before the page extraction option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1464783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392048] Re: File not printed Exception: unknown object type inspecting /Contents key in page dictionary
Exception is thrown in libqpdf ** Package changed: cups-filters (Ubuntu) = qpdf (Ubuntu) ** Also affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392048 Title: File not printed Exception: unknown object type inspecting /Contents key in page dictionary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1392048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392048] Re: File not printed Exception: unknown object type inspecting /Contents key in page dictionary
Per PDF Spec, the /contents key in a Page dictionary is optional. The attached pdf's page 9 has no /contents key. But QPdfObjectHandle::getPageContents() throws an exception; cups-filter (pdftopdf) calls it via QPDFObjectHandle::addPageContents(). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392048 Title: File not printed Exception: unknown object type inspecting /Contents key in page dictionary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1392048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392048] Re: File not printed Exception: unknown object type inspecting /Contents key in page dictionary
/Contents is the correct spelling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392048 Title: File not printed Exception: unknown object type inspecting /Contents key in page dictionary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1392048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263784] Re: PDF form data is blank when printed with lp
cups-filter's pdftopdf before around 1.0.21 was based on poppler, not qpdf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263784 Title: PDF form data is blank when printed with lp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1263784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263784] Re: PDF form data is blank when printed with lp
You seem to have a quite old version of cups-filters (=1.0.20 i think). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263784 Title: PDF form data is blank when printed with lp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1263784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259240] Re: pdftopdf doesn't perform software collate
Fixed in bzr revision 7145. ** Changed in: cups-filters (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259240 Title: pdftopdf doesn't perform software collate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1259240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259240] Re: pdftopdf doesn't perform software collate
** Changed in: cups-filters (Ubuntu) Status: New = In Progress ** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) = Tobias Hoffmann (smilingthax) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259240 Title: pdftopdf doesn't perform software collate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1259240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221520] Re: Blank pages inserted in duplex print job
No full analysis yet, but a first point: The line was deleted in the commit, not added. Therefore it is correct, that it is also missing later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221520 Title: Blank pages inserted in duplex print job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1221520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198332] Re: Crash when using multi-touch input
** Attachment added: x server log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1198332/+attachment/3726261/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198332 Title: Crash when using multi-touch input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1198332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198332] [NEW] Crash when using multi-touch input
Public bug reported: Reproducible crash: 1) start x 2) (terminal): xinput test-xi2 10 [10 is the device id, see below] 3) use touch device on the window a bit, use more than 2 fingers, and occassionally click into the terminal window 4) xserver segfaults after at most a few tries of 3), i.e. less than 15 seconds of trying Output of xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8[slave pointer (2)] ⎜ ↳ Advanced Silicon S.A CoolTouch(TM) System id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ Cherry GmbH id=9[slave keyboard (3)] Affected Versions (summary): xserver-xorg-core_1.14.1-0ubuntu0.8_i386 xserver-xorg-core_1.13.3-0ubuntu6_i386 My base system is actually debian testing with a custom 3.10-rc4 x86_64 kernel, but the crash is clearly related to the (manually installed and newer) ubuntu xorg packages and not the base system. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Attachment added: gdb backtrace https://bugs.launchpad.net/bugs/1198332/+attachment/3726260/+files/xorg-bt-full.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198332 Title: Crash when using multi-touch input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1198332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154318] Re: pdftopdf assert failure: EPSON-Epson-Stylus-SX430: filter/pdftopdf/qpdf_pdftopdf.cc:34: Rotation getRotate(QPDFObjectHandle): Assertion `rot==0.0' failed.
The assert triggers because the PDF to be processed contains a /Rotation key which is not equal to 0, 90, 180 or 270. Basically there are three possibilities: 1) The pdf uses a value not allowed by the pdf specification. 2) The value is close, but not exactly equal to one of the above rotation values 3) The value is not normalized to [0;360) but is e.g. -90. So to fix this I have to know what value the offending PDF uses instead, maybe you can attach the file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154318 Title: pdftopdf assert failure: EPSON-Epson-Stylus-SX430: filter/pdftopdf/qpdf_pdftopdf.cc:34: Rotation getRotate(QPDFObjectHandle): Assertion `rot==0.0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1154318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154318] Re: pdftopdf assert failure: EPSON-Epson-Stylus-SX430: filter/pdftopdf/qpdf_pdftopdf.cc:34: Rotation getRotate(QPDFObjectHandle): Assertion `rot==0.0' failed.
Sure, there should not... and when compiled with -DNDEBUG it actually would not exit, but just assume 0.0 degrees rotation... The assert basically was there, because this particular function only implemented the simple cases (taking care of nearly all pdfs in the wild) and was not touched since then... I've updated bzr (revision 7046) to handle at least all multiples of 90 correctly (i.e. also negative ones) now and throw an exception when encountering a still unexpected value. This may or may not fix pdftopdf for this particular pdf. Either try the offending pdf with the current bazaar version of cups-filters (and watch out for 'Unexpected /Rotation value: ...' exceptions in the log), or I can check the pdf file (and make further changes to pdftopdf, if necessary). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154318 Title: pdftopdf assert failure: EPSON-Epson-Stylus-SX430: filter/pdftopdf/qpdf_pdftopdf.cc:34: Rotation getRotate(QPDFObjectHandle): Assertion `rot==0.0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1154318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1137438] Re: texttopdf crashes while printing on ubuntu 11.10
Actually two issues are involved here, a corrupt pdf is generated for
certain utf-8 title-parameters (where the filename is passed in), and,
when 'prettyprint' is enabled, a texttopdf assertion fails('crash'),
when different utf-8 ranges are used in the title.
Both are fixed in bazaar revision 7041.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1137438
Title:
texttopdf crashes while printing on ubuntu 11.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1137438/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 923955] Re: pdftopdf filter fails to output form field values
Sorry, I forgot to subscribe and did not get your comment by mail... I think a recent evince will directly send pdf (and not ps) to cups. But it will 'rewrite' quite heavily. And yes, PDF is the new internal default format in the linux printing chain. This has more to do with having the appropriate cups-filters than the cups version, though. AFAICT it probably was the pdf-ps pipeline. But, regarding this bug, I have tracked down the problem in libqpdf to the use of stale object-cache entries, and reported it to the author; the next libqpdf update will fix this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/923955 Title: pdftopdf filter fails to output form field values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/923955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 923955] Re: pdftopdf filter fails to output form field values
Form values are also lost with the old pdftopdf implementation (used in cups-filters before 1.0.21). Probably only the pdf-ps workflow ever worked. The form values are also lost by just using qpdf to 'non-destructively' rewrite the pdf. Therefore the problem is already present in the underlying libqpdf. The provided pdf files all use xref-streams, which I'm currently not able to accurately debug. I have some faint memories that to enable form-filling with Adobe Reader the original pdf has to be specially 'signed', and this signature can only be generated by the Adobe Acrobat Professional application... this might play a role here. Another thing: When I use evince to print the form, it seems to work. Could it be that the problem only occurs when using Adobe Reader to fill and/or print the form? Or at least that it works, when evince is used to fill/print? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/923955 Title: pdftopdf filter fails to output form field values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/923955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111292] Re: Duplex printing on Ubuntu 12.10 is taking additional blank paper with 'scale to fit' option selected
Till, that's very strange. I can only reproduce the bug with rev 7035, but not with 7036. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/292 Title: Duplex printing on Ubuntu 12.10 is taking additional blank paper with 'scale to fit' option selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111292] Re: Duplex printing on Ubuntu 12.10 is taking additional blank paper with 'scale to fit' option selected
A very similar problem has been fixed very recently, https://bugs.linuxfoundation.org/show_bug.cgi?id=1088 which is fixed in bazaar revision 7036. Please check if the bug still occurs with the current bzr version of pdftopdf/cups-filters. Tobias ** Bug watch added: bugs.linuxfoundation.org/ #1088 https://bugs.linuxfoundation.org/show_bug.cgi?id=1088 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/292 Title: Duplex printing on Ubuntu 12.10 is taking additional blank paper with 'scale to fit' option selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024435] Re: [MIR] qpdf
I'm the one currently working on the new libqpdf-based pdf- implementation. The old implementation of pdftopdf does not duplicate that much of poppler, but it has a class structure that /parallels/ the poppler document representation, because poppler was never built to /output/ pdfs, but pdftopdf has to! This is done by all the P2P*-classes in pdftopdf: They can actually recreate the pdf-objects that poppler parsed. So there is quite tight coupling of pdftopdf to the poppler internals, but there are much less eyes looking at pdftopdf than are looking at the poppler-code. This make maintainance of pdftopdf tedious across changes between poppler versions. IMO this current state does not benefit security at all. qpdf is extensively tested, and built for the job: It provides an c ++-object-oriented interface to the pdf-objects, but does not interpret their contents, except for the very basic structure (root catalog, pages tree), and neither does the new pdftodf -- because it does not have to. Basically all the transformations can be done without actually looking at the exact values from the input pdf; it's either pass-it-through or throw-it-away. That means: The actual code surface actually exposed to potentially dangerous inputs is quite small. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024435 Title: [MIR] qpdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1024435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
