Bug 196722 - printing in okular doesnt work, all pages are cut off
Summary: printing in okular doesnt work, all pages are cut off
Status: RESOLVED DUPLICATE of bug 196590
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-16 09:48 UTC by Felix Michel
Modified: 2009-06-16 16:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
document to illustrate printing problem (201.86 KB, application/pdf)
2009-06-16 12:37 UTC, Felix Michel 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Michel 2009-06-16 09:48:11 UTC 
Version:           0.8.80 (using KDE 4.2.90)
OS:                Linux
Installed from:    Unspecified Linux

If i want to print a pdf-documet all pages are cut off. doing a landscape print, the printing process begins in the middle of the pages and there is a big margin on the bottom. this way the printed files are absolutely of no use. doing a portrat print, the big margin is on the top and the pages are cut off on the bottom and one side.

that is really annoying, because i cant print anymore with my favorite pdf viewer.
Comment 1 Pino Toscano 2009-06-16 10:50:15 UTC 
Did it work in previous versions?
Also, can you show an example or what you have and what you get?
Comment 2 Felix Michel 2009-06-16 12:37:07 UTC 
Created attachment 34575 [details]
document to illustrate printing problem
Comment 3 Felix Michel 2009-06-16 12:42:12 UTC 
yes, in previous versions it worked.

if i print this document (see attachement above) i got a big margin on the left and on the top (5.5 cm and 7 cm). I would send you an image of the printed document, but unfortunately linux doesnt recognize my digicam. sorry.

do you need some more information?
Comment 4 Pino Toscano 2009-06-16 16:14:57 UTC 

*** This bug has been marked as a duplicate of bug 196590 ***