Bug 299050

Summary:	document shows blank print preview
Product:	[Applications] okular	Reporter:	Jon Burgess <jburgess777>
Component:	PDF backend	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aacid
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
URL:	http://www.audi.co.uk/content/dam/audi/production/PDF/PriceAndSpecGuides/a3-s3.pdf
Latest Commit:		Version Fixed In:

Description Jon Burgess 2012-04-29 18:18:08 UTC

The file at the URL above displays OK when opened but the print preview is blank.



Reproducible: Always

Steps to Reproduce:
1. Open file
2. File -> Print Preview
3.
Actual Results:  
Preview window appears but all the pages are blank

Expected Results:  
The document to appear

This happens for me with Okular on both F16 and the F17 beta release. 
The same document opens, previews & prints OK in evince.

The messages below appear on stdout/stderr:

[jburgess@shark audi]$ okular a3-s3.pdf 
typecheck -20
okular(4987)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [792x612]
QImage::scaled: Image is a null image
typecheck -20
okular(4987)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [792x612]
QImage::scaled: Image is a null image
typecheck -20
okular(4987)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [792x612]
QImage::scaled: Image is a null image
typecheck -20
okular(4987)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [792x612]
QImage::scaled: Image is a null image
typecheck -20
okular(4987)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [78x60]
QImage::scaled: Image is a null image
typecheck -20

Comment 1 Albert Astals Cid 2012-04-29 18:40:43 UTC

It's not an Okular bug but a poppler bug (the library we use to deal with pdf). Anyway it works with poppler 0.19.4, once your distribution updates to poppler >= 0.20 this fix will be gone