Bug 242285

Summary:	Okular should report PostScript errors
Product:	[Applications] okular	Reporter:	Christopher Yeleighton <giecrilj>
Component:	PS backend	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED WORKSFORME
Severity:	wishlist
Priority:	NOR
Version:	0.9.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2010-06-20 18:58:00 UTC

Version:           0.9.5 (using KDE 4.3.5) 
OS:                Linux

According to PLRM_3.7.7 "Job Execution Environment", a print server should display an error message if a job causes an unhandled PostScript error.

Reproducible: Always

Steps to Reproduce:
1. 
Display the following file in Okular:
%!PS-Adobe-3.0
exit


Actual Results:  
1. blank page

Expected Results:  
1. error message: invalidexit

OS: Linux (x86_64) release 2.6.31.12-0.2-desktop
Compiler: gcc

Comment 1 Pino Toscano 2010-06-20 19:09:40 UTC

$ cat >broken.ps <<EOF
> %!PS-Adobe-3.0
> exit
> EOF
$ okular broken.ps
[...]
okular(7688)/kdecore (trader) KMimeTypeTrader::query: query for mimeType  "application/postscript" ,  "okular/Generator"  : returning  1  offers
invalidexit -8
okular(7688)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [1005x1300]
QImage::scaled: Image is a null image
invalidexit -8
okular(7688)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [989x1279]
QImage::scaled: Image is a null image
invalidexit -8
okular(7688)/okular (Spectre) GSRendererThread::run: Generated image does not match wanted size: [0x0] vs requested [267x346]
QImage::scaled: Image is a null image
[...]

So, errors are already reported on stderr on console. I don't see anything that says that errors must be shown directly "in your face" to the user.

Comment 2 Christopher Yeleighton 2010-06-21 08:45:43 UTC

(In reply to comment #1)
> So, errors are already reported on stderr on console. I don't see anything that
> says that errors must be shown directly "in your face" to the user.

Please add a note to that account to the manual; these messages go to .xsession-errors where they are not immediately visible.

Also, a message like "invalidexit -8" seems to be too terse; it does not identify the sending application (which can usually be inferred from other interleaved messages) or the offending file (which the operator might be able to guess).