Bug 94756

Works fine here, which poppler version are you using?

0.42.0 and Okular 0.24.2

Building with -fsanitize=undefined shows:

poppler-0.42.0/goo/GooString.cc:166:23: runtime error: null pointer passed as argument 2, which is declared to never be null
poppler-0.42.0/poppler/XRef.cc:1199:19: runtime error: load of value 774974790, which is not a valid value for type 'CryptAlgorithm'
poppler-0.42.0/poppler/XRef.cc:427:24: runtime error: load of value 774974790, which is not a valid value for type 'CryptAlgorithm'
poppler-0.42.0/splash/SplashScreen.cc:380:57: runtime error: null pointer passed as argument 1, which is declared to never be null
poppler-0.42.0/splash/SplashScreen.cc:380:57: runtime error: null pointer passed as argument 2, which is declared to never be null
poppler-0.42.0/poppler/TextOutputDev.cc:3357:77: runtime error: null pointer passed as argument 1, which is declared to never be null

pdftocairo and pdftoppm work fine. So it might be an Okular specific issue.

Can you attach a screenshot?

Created attachment 122650 [details]
screenshot

Do you build poppler yourself or get it from your distro? If you build it yourself can you try qt4/demos/poppler_qt4viewer and qt4/tests/test-poppler-qt4 and see if they have the same problem?

(In reply to Albert Astals Cid from comment #7)
> Do you build poppler yourself or get it from your distro? If you build it
> yourself can you try qt4/demos/poppler_qt4viewer and
> qt4/tests/test-poppler-qt4 and see if they have the same problem?

qt4/demos/poppler_qt4viewer works fine.

We can continue this over at bugs.kde.org if you want but honestly i can't see what would make it break so you get to decide where this bug gets stuck until someone has a really great idea of what may be wrong.

org.kde.okular.core: request observer=0xecb1f80 1044x584@3
org.kde.okular.core: sending request observer=0xecb1f80 1044x584@3 async == true isTile == false
org.kde.okular.generators.pdf: [Poppler] "Error: unable to allocate 0 entries"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: Couldn't find trailer dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: Weird page contents"
org.kde.okular.generators.pdf: [Poppler] "Error: unable to allocate 0 entries"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: font resource is not a dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: Couldn't find trailer dictionary"
org.kde.okular.generators.pdf: [Poppler] "Error: Weird page contents"

Those are exactly the same errors 
qt4/demos/poppler_qt4viewer should give you, otherwise something is very broken on your system.

The reason for blank pages is the solution for bug 92508, Albert. Seems as if You are using okular with an older poppler.
In the catalog dict of that PDF are some object referenced (JavaScript, Outlines) which are not part of the PDF.
But because the xref reconstruction algorithm is not able to reconstruct any xref, the xref table is destroyed and the xref structure is no more usable.

And the reconstruction algorithm doesn't work for that PDF because it doesn't use blanks as delimiter but newlines, i.e. instead of

4 0 obj

there is

4
0
obj

Never saw something like this, but it seems to be legal. I will work on a solution.

Created attachment 122699 [details] [review]
Allow newlines in '<num> <gen> obj' sequence

This patch solve it

(In reply to Thomas Freitag from comment #13)
> Created attachment 122699 [details] [review] [review]
> Allow newlines in '<num> <gen> obj' sequence
> 
> This patch solve it

Thanks. It works fine now.

(In reply to Thomas Freitag from comment #12)
> The reason for blank pages is the solution for bug 92508, Albert. Seems as
> if You are using okular with an older poppler.
> In the catalog dict of that PDF are some object referenced (JavaScript,
> Outlines) which are not part of the PDF.
> But because the xref reconstruction algorithm is not able to reconstruct any
> xref, the xref table is destroyed and the xref structure is no more usable.
> 
> And the reconstruction algorithm doesn't work for that PDF because it
> doesn't use blanks as delimiter but newlines, i.e. instead of
> 
> 4 0 obj
> 
> there is
> 
> 4
> 0
> obj
> 
> Never saw something like this, but it seems to be legal. I will work on a
> solution.

So you mean that we break the xref while trying to reconstruct it?

ouch

*** Bug 94830 has been marked as a duplicate of this bug. ***

Pushed