The tested snaps indeed use the same libpoppler version as found in
18.04.
I have created a 20.04 boot medium and tested evince using the "try
Ubuntu without installation". This did indeed work, so I stand corrected
that the bug is fixed in current Ubuntu releases.
The evince version in 20.04 is
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
Trying different free software PDF readers, at least some of which use
the same PDF library as evince, does not produce any crashes, but error
(or warning) messages for some:
- xpdf works without messages.
- okular works without messages (and can extract the embedded XML).
- Firefox works
To test newer versions of evince I have installed evince via the snap
store.
After installation via snap, the snap version can be started using its
different program icon (I hope you can understand what I mean, I clicked
the "9 dots" icon in the bottom of the task bar on the left, typed
"evince",
A stack trace and some additional crash info with a different recent RFC
PDF document:
$ section -i '^(problem|proccmdline|stacktrace|segv|signal)'
/var/crash/_usr_bin_evince.1000.crash
ProblemType: Crash
ProcCmdline: evince /tmp/mozilla_auerswald0/rfc8792.pdf
Signal: 11
SegvAnalysis:
Segfault
The problem may be related to how exactly an XML file is embedded inside the
RFC PDF documents.
See
https://mailarchive.ietf.org/arch/msg/tools-discuss/12Efvwr7KXrgjVTWpaR4pa2hv-U
.
Removing the embedded file with 'pdftk rfc8798.pdf cat output
rfc8798-no_xml.pdf' results in a PDF that evince
** Bug watch added: Debian Bug tracker #963813
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963813
** Also affects: evince (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963813
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Apport showed: "evince crashed with SIGSEGV in g_string_free()".
In the other evince crash bug report, I was asked to provide a stack
trace. Here it is for this specific (publicly accessible) file:
Stacktrace:
#0 0x7fda9d0971b0 in g_string_free () at
** This bug is no longer a duplicate of bug 1849888
evince crashes (segmentation fault) when opening file rfc8655.pdf and other
new-format Internet standards
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
This problem still affects 18.04 ("bionic"), as is obvious from the bug
history.
A similar, but different, problem still affects current evince versions,
including those newer than the version in 19.10, see
https://mailarchive.ietf.org/arch/msg/tools-discuss/hgenvnKeP9zX-
IBX5FyD6zyEkmI/ .
*** This bug is a duplicate of bug 1849888 ***
https://bugs.launchpad.net/bugs/1849888
Thanks for looking at this bug report.
While this crash looks similar, and all the other problematic RFC
documents still crash the evince version in 18.04, there is another
report of issues with this
Public bug reported:
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
To add a bit of background: the IETF (standards body for the Internet)
decided to change the format of their newly published standards from
ASCII text to XML. From this XML both HTML and PDF versions are
generated (and a text version which may omit diagrams / pictures). The
PDF version cannot be
The problem seems to lie in the new format for IETF RFCs, i.e., all
official PDF files of RFCs released using the new format result in
evince crashes:
https://www.rfc-editor.org/rfc/rfc8651.pdf
https://www.rfc-editor.org/rfc/rfc8653.pdf
https://www.rfc-editor.org/rfc/rfc8654.pdf
Public bug reported:
When trying to display the PDF file rfc8655.pdf from
https://tools.ietf.org/pdf/rfc8655.pdf evince crashes:
$ evince rfc8655.pdf
Segmentation fault (core dumped)
I would have expected the PDF file to be displayed. Instead, evince
crashed and did not display the
Public bug reported:
The pager of the ExtremeXOS switch operating system's CLI uses the (not
strictly correct) control sequence "CSI60;D" to delete the pager prompt
before displaying the next line of output. The correct control sequence
would be "CSI60D" (without a semicolon), but basically all
16 matches
Mail list logo
