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
