[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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 3.36.0 (older than the latest/candidate snap), libpoppler and poppler-utils are version 0.86.1 (newer than in the snaps, or in Debian). So this does look like a poppler rather than evince problem. Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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 Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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 without messages (and can extract the embedded XML).
- Chrome works without messages.
- pdfdetach (from poppler-utils) can extract the embedded XML file.
- pdftk can extract the XML.
- mupdf works with error and warning messages:
error: Unable to read ICC workflow
warning: Attempt to read Output Intent failed
- gv works with error messages:
Error: ignoring annotation with scale factor of 0
Output may be incorrect.
Error: Ignoring invalid annotation, output may be incorrect.
Error: ignoring annotation with scale factor of 0
Output may be incorrect.
Error: Ignoring invalid annotation, output may be incorrect.
The PDF document can be transformed to be acceptable to evince: recreating the
PDF with pdftk results in a file that works without errors, even in evince.
But 'mutool clean' does not change anything.
This issue seems to be specific to evince, and affect many versions,
including recent ones.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1885313
Title:
evince crashes when opening rfc8798.pdf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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", found two versions using different icons, and verified the version via "Show Details"). * 3.34.2+git4.91cbe4fe (from 2020-06-01) crashes with all the RFC PDF documents of this bug and bug #1849888 (which does cast some doubt about that bug being fixed in evince version 3.34.1-1). * 3.36.6+git2.ce03847a (from 2020-06-27) crashes as well. * 3.37.2+git65.582b220e (from 2020-06-30) does not start, so result for the problematic RFC PDFs. So at least _this_ bug is relevant to more recent versions of evince than the 18.04 LTS default. For the default latest/stable channel the snap package shows the following information: $ sudo snap info evince name: evince summary: Document viewer for popular document formats publisher: Ken VanDine store-url: https://snapcraft.io/evince contact: https://bugs.launchpad.net/ubuntu/+source/evince/+bugs?field.tag=snap license: unset description: | This is a document viewer for the GNOME desktop. It supports the following document formats: PDF, PS, EPS, XPS, DjVu, TIFF, DVI (with SyncTeX), and Comic Books archives (CBR, CBT, CBZ, CB7). commands: - evince - evince.evince-previewer - evince.evince-thumbnailer snap-id: EDFg87ESUg9sAIlm0Vm5Wmr0LjiEonSm tracking: latest/stable refresh-date: today at 13:17 CEST channels: latest/stable:3.34.2+git4.91cbe4fe 2020-06-01 (434) 8MB - latest/candidate: 3.36.6+git2.ce03847a 2020-06-27 (469) 8MB - latest/beta: ↑ latest/edge: 3.37.2+git65.582b220e 2020-06-30 (474) 8MB - installed: 3.34.2+git4.91cbe4fe (434) 8MB - ** Tags added: bionic snap -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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 happened at: 0x7f83eb0061b0 : mov
(%rdi),%rbp
PC (0x7f83eb0061b0) ok
source "(%rdi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%rbp" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Stacktrace:
#0 0x7f83eb0061b0 in g_string_free () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f83d8103073 in () at /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#2 0x7f83eb2c4012 in g_object_unref () at
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x7f83d834225e in () at
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#4 0x7f83ed713b7a in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#5 0x7f83ed715c02 in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#6 0x7f83eb00c175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x7f83ea9e26db in start_thread (arg=0x7f83c6456700) at
pthread_create.c:463
pd = 0x7f83c6456700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140203943880448,
-5947558141446818078, 140203943877760, 0, 93867129415456, 140729791250992,
5940683226884634338, 5940760682756601570}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#8 0x7f83ea70b88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
StacktraceAddressSignature:
/usr/bin/evince:11:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4+6e1b0:/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8.9.0+28073:/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.4+15012:/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so+c25e:/usr/lib/x86_64-linux-gnu/libevview3.so.3.0.0+1db7a:/usr/lib/x86_64-linux-gnu/libevview3.so.3.0.0+1fc02:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4+74175:/lib/x86_64-linux-gnu/libpthread-2.27.so+76db:/lib/x86_64-linux-gnu/libc-2.27.so+12188f
StacktraceTop:
g_string_free () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
() at /usr/lib/x86_64-linux-gnu/libevview3.so.3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1885313
Title:
evince crashes when opening rfc8798.pdf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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 can display. Re-adding the embedded XML file with 'pdftk rfc8798-no_xml.pdf attach_file rfc8798.xml output rfc8798-pdftk-embed.pdf' again results in a PDF that works fine with evince. Thus it is not the fact that an XML file is embedded that results in the evince crash, but rather the exact procedure used respective the specific result of document processing as done when creating a PDF rendering of an RFC for publication. This still is a bug in evince, because evince is not supposed to perform invalid memory accesses and crash. Especially since other PDF viewers (e.g., Firefox) can display the PDF without visible problems (MuPDF creates error and warning messages, but still displays the PDF correctly). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
** 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 you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
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
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7fda743b1073 in () at /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#2 0x7fda9d355012 in g_object_unref () at
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x7fda745f025e in () at
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#4 0x7fda9f7a4b7a in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#5 0x7fda9f7a6c02 in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#6 0x7fda9d09d175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x7fda9ca736db in start_thread (arg=0x7fda6bfff700) at
pthread_create.c:463
pd = 0x7fda6bfff700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140576091535104,
-8300492376050083283, 140576091532416, 0, 94728809145744, 140737090109552,
8321084030215936557, 8321389215404677677}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#8 0x7fda9c79c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
ThreadStacktrace:
.
Thread 15 (Thread 0x7fda767fc700 (LWP 5914)):
#0 0x7fda9c796839 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fda9d0bb87a in g_cond_wait_until () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fda9d048571 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fda9d09db14 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fda9d09d175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fda9ca736db in start_thread (arg=0x7fda767fc700) at
pthread_create.c:463
pd = 0x7fda767fc700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140576267683584,
-8300492376050083283, 140576267680896, 0, 94728808515360, 140737090109328,
8321058738764143149, 8321389215404677677}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fda9c79c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
.
Thread 14 (Thread 0x7fda932ad700 (LWP 5905)):
#0 0x7fda9c78fbf9 in __GI___poll (fds=0x5627c4ba6de0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1 0x7fda9d0755c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fda9d075962 in g_main_loop_run () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fda9d887276 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x7fda9d09d175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fda9ca736db in start_thread (arg=0x7fda932ad700) at
pthread_create.c:463
pd = 0x7fda932ad700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140576748656384,
-8300492376050083283, 140576748653696, 0, 94728804033392, 140737090105824,
8321416796765837869, 8321389215404677677}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fda9c79c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
.
Thread 13 (Thread 0x7fda76ffd700 (LWP 5913)):
#0 0x7fda9c796839 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fda9d0bb87a in g_cond_wait_until () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fda9d048571 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fda9d09db14 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fda9d09d175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fda9ca736db in start_thread (arg=0x7fda76ffd700) at
pthread_create.c:463
pd = 0x7fda76ffd700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140576276076288,
-8300492376050083283, 140576276073600, 0, 94728809084704, 140737090109328,
8321059842033867309, 8321389215404677677}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fda9c79c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
.
Thread 12 (Thread 0x7fda74ff9700 (LWP 5917)):
#0 0x7fda9c796839 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fda9d0bb87a in g_cond_wait_until () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fda9d048571 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fda9d09db14 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fda9d09d175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fda9ca736db in start_t
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
** 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. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards
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/ .
Please see bug #1885313
(https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313) which is
actually not a duplicate of this one.
Thanks,
Erik
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1849888
Title:
evince crashes (segmentation fault) when opening file rfc8655.pdf and
other new-format Internet standards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] Re: evince crashes when opening rfc8798.pdf
*** 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 specific file on an IETF mailing list: https://mailarchive.ietf.org/arch/msg/tools-discuss/hgenvnKeP9zX- IBX5FyD6zyEkmI There it is reported that evince versions 3.30.2 and 3.36.5 cannot open _this_ file (https://www.rfc-editor.org/rfc/rfc8798.pdf). Since the evince in 19.10 that supposedly fixes the issue in bug #1849888 is 3.34.1-1, this bug is with a high probability _not_ a duplicate of said bug. It probably is related, but not the same. And while initially all new format RFCs crashed evince, in the interim many additional new format RFCs have been published, and not all of them crash evince, not even the version in 18.04. Looking at the evince versions in 20.04 (3.36.0-2) and the in- development "groovy" (3.36.5-2), this issue may well affect all the bleeding edge Ubuntu versions as well, opposed to #1849888. Thus I do think that this bug is distinct from #1849888 and not a duplicate. Thanks, Erik -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885313] [NEW] evince crashes when opening rfc8798.pdf
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 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". ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1885313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf
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 read on Ubuntu 18.04 with default configuration, because the default document viewer evince crashes when opening the file. ** Summary changed: - evince crashes (segmentation fault) when opening file rfc8655.pdf + 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. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf
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 https://www.rfc-editor.org/rfc/rfc8655.pdf $ ls -a . .. $ wget -nv https://www.rfc-editor.org/rfc/rfc8651.pdf https://www.rfc-editor.org/rfc/rfc8653.pdf https://www.rfc-editor.org/rfc/rfc8654.pdf https://www.rfc-editor.org/rfc/rfc8655.pdf 2019-11-05 09:53:01 URL:https://www.rfc-editor.org/rfc/rfc8651.pdf [137041/137041] -> "rfc8651.pdf" [1] 2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8653.pdf [128896/128896] -> "rfc8653.pdf" [1] 2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8654.pdf [102866/102866] -> "rfc8654.pdf" [1] 2019-11-05 09:53:02 URL:https://www.rfc-editor.org/rfc/rfc8655.pdf [325847/325847] -> "rfc8655.pdf" [1] FINISHED --2019-11-05 09:53:02-- Total wall clock time: 2,3s Downloaded: 4 files, 678K in 1,0s (654 KB/s) $ evince rfc8651.pdf Segmentation fault (core dumped) $ evince rfc8653.pdf Segmentation fault (core dumped) $ evince rfc8654.pdf Segmentation fault (core dumped) $ evince rfc8655.pdf Segmentation fault (core dumped) Older PDFs work fine, e.g., https://www.rfc- editor.org/rfc/pdfrfc/rfc8649.txt.pdf . The built-in PDF viewer of Firefox can display all the above PDF files. The built-in PDF viewer of Chrome can display all the above PDF files. The MuPDF PDF viewer can display all the above PDF files. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849888] [NEW] evince crashes (segmentation fault) when opening file rfc8655.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 document. The built-in PDF renderer of Firefox 70.0 does display the PDF correctly. Since the segmentation fault hints at a memory management error triggered by external input this may have security implications. I did not investigate this any further. I do not set the "This bug is a security vulnerability" flag because I do not know if it really is (it probably is, but I have no proof) and I do not want this bug report to be private. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ 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 $ evince --version GNOME Document Viewer 3.28.4 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade from 16.04 resulted in a non-booting system). ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1590674] [NEW] ExtremeXOS pager does not work correctly in gnome-terminal, because gnome-terminal ignores the CSI CUB control sequence used by ExtremeXOS
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 other terminal emulators accept both forms (tested with screen, xterm, rxvt, PuTTY (on Windows), Mac OS X terminal). This affects working with Extreme Networks switches using the default terminal application in Ubuntu. Windows (PuTTY) and Mac OS X (terminal application) users do not experience a similar problem. A simple test to check the control sequence is: printf 'CSI CUB with semicolon is not\x1b[4;D accepted\n' In gnome-terminal this prints: "CSI CUB with semicolon is not[4;D accepted" In screen, xterm, and rxvt this prints: "CSI CUB with semicolon is accepted" Changing the above command to not contain a semicolon works on gnome- terminal as well: printf 'CSI CUB without semicolon is not\x1b[4D accepted\n' In gnome-terminal, screen, xterm, and rxvt this prints "CSI CUB without semicolon is accepted" Thus gnome-terminal breaks backwards-compatibility by a too-pedantic interpretation of VT100 control sequences. As a result it is less convenient to use Ubuntu when working with products of Extreme Networks than using Windows or Mac OS X. If some one wants to verify this with ExtremeXOS, the EXOS VM available on GitHub (https://github.com/extremenetworks/Virtual_EXOS) can be used. Info about my system: $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.6.2-0ubuntu1 Candidate: 3.6.2-0ubuntu1 Version table: *** 3.6.2-0ubuntu1 0 500 http://ftp.uni-kl.de/pub/linux/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status This happened on Ubuntu 12.04 LTS as well. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1590674 Title: ExtremeXOS pager does not work correctly in gnome-terminal, because gnome-terminal ignores the CSI CUB control sequence used by ExtremeXOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1590674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
