The Debian bug report clearly shows that current unstable still exhibits
the bug.

Since Ubuntu is based on unstable, every Ubuntu version, released or in
development, still exhibits this bug.

As before, the bug is closed as "fixed", but it is not fixed.

The first possible fix in an LTS release is in 22.04 LTS, if upstream
picks the problem up and really fixes it. But since this report seems to
show that it already is fixed, they might be lured into thinking it is
fixed already. It is not.

Even if we assume that the bug was fixed in 19.10 and then re-appeared,
and possibly fixed in some experimental code base, just closing this bug
is the surest way to have it re-appear again, because it was never
diagnosed and knowingly fixed, but rather happened to not show itself in
some random version of the software.

This is very frustrating, and one of the reasons many people still think
commercial proprietary software is of better quality than free software
(as evidenced, e.g., in the IETF mailing list thread[1]). :-(

[1] https://mailarchive.ietf.org/arch/msg/tools-
discuss/vIR4w4Qgj796wcTkiNtK6ljMxss/

The poppler-using xpdf in 18.04 does not have this issue. The tools from
poppler-utils work fine with the PDF documents in question. So is it
really an issue in poppler? Or rather in the way evince uses poppler? I
am not familiar with either code base, so I have no idea.

The GNOME Document Viewer "evince" stands out as the only PDF viewer
that actually crashes on those PDFs. Others display the PDFs, with some
(e.g., MuPDF and gv) producing warning and/or error messages (but still
correctly displaying the document). It also stands out as the default
PDF viewer in Ubuntu.

It is not a problem of PDF attachments not working in poppler based PDF
viewers, because (using, e.g., pdftk) it is possible to take the
problematic PDFs, extract the attachment, create a new PDF without
attachment, but otherwise the same contents, and then (re-)attach the
file extracted in the first step. The result works fine in evince (and
does not produce error nor warning messages in MuPDF).

I am sorry for venting my frustration.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1885313

Title:
  evince crashes when opening rfc8798.pdf

Status in poppler package in Ubuntu:
  Fix Released
Status in evince package in Debian:
  New

Bug description:
  evince reproducabely crashes when opening the file rfc8798.pdf from
  https://www.rfc-editor.org/rfc/rfc8798.pdf:

  $ evince --version
  GNOME Document Viewer 3.28.4
  $ evince rfc8798.pdf
  Segmentation fault (core dumped)
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

  Required information:

  1) Ubuntu release info:
  $ lsb_release -rd
  Description:    Ubuntu 18.04.4 LTS
  Release:        18.04

  2) Package version info:
  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1.2
    Candidate: 3.28.4-0ubuntu1.2
    Version table:
   *** 3.28.4-0ubuntu1.2 500
          500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
          500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
          100 /var/lib/dpkg/status
       3.28.2-1 500
          500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) Expected outcome:
  I expected evince to successfully open the PDF, allowing me to read the 
document.

  4) Observed behavior:
  The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation 
fault".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to