Bug 94446 - PDF pages shown out of order
Summary: PDF pages shown out of order
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-08 23:12 UTC by laughingcedar
Modified: 2018-08-20 21:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
the PDF file that evince views improperly (373.42 KB, text/plain)
2016-03-08 23:12 UTC, laughingcedar
Details

Description laughingcedar 2016-03-08 23:12:16 UTC
Created attachment 122171 [details]
the PDF file that evince views improperly

I filed this as a bug against evince (https://bugzilla.gnome.org/show_bug.cgi?id=763346) and was told it's a poppler problem, and asked to re-file it here. 

I'm viewing a PDF (attached) with evince, and it's displaying the pages all out of order. Unfortunately this PDF doesn't have printed page numbers, which would make it easier to describe, so here's a spot where it's obvious that the pages are all out of order:

Page 7 is the end of the conclusion and the acknowledgements (which should be page ~30 of this scientific paper)
Page 8 is a page from the methods section. 
Page 9 is the figure captions. 
And page 10 is back into the methods.

The PDF views normally on other systems -- I tried it on a Mac and on Gmail's web-interface preview, and the pages all display in the proper order there.

The problem recurs on a second Linux computer, also running Fedora 22 and Evince 3.16.1 (the latest version in the F22 repository). The incorrect order appears to be the same on both computers.

Below is output from poppler utils:

$ pdftoppm orig.pdf orig
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (70 0) is not a pageDict
Syntax Warning: Failed parsing page 8 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
Syntax Warning: Failed parsing page 10 using hint tables
Syntax Warning: Object (116 0) is not a pageDict
[...]
Comment 1 GitLab Migration User 2018-08-20 21:48:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/77.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.