Bug 180280 - Okular Default Paper Size is A4
Summary: Okular Default Paper Size is A4
Status: RESOLVED DUPLICATE of bug 177360
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.7.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-10 18:11 UTC by Gerald Cox
Modified: 2009-01-13 20:08 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Cox 2009-01-10 18:11:38 UTC 
Version:           0.7.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

When trying to print a PDF file, printer settings for Okular are "stuck" at A4.  Cannot find way to change default to US Letter.  I did find the method to change the print size for a individual file when requesting to print, however even though I am able to change to US Letter size, when the file is printed, the instructions to the printer are A4, e.g. I get a message on the printer to load A4 paper.
Comment 1 Kevin Kofler 2009-01-10 19:52:48 UTC 
See also the downstream Fedora bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=469498
Comment 2 Pino Toscano 2009-01-10 20:05:18 UTC 
What about trying KDE 4.1.4 or KDE 4.2beta2?
Comment 3 John Layt 2009-01-12 21:41:55 UTC 
Looks to me like a duplicate of http://bugs.kde.org/show_bug.cgi?id=177360.  Can you confirm that that selecting Print / Properties / Advanced gives you a blank advanced settings page?  Or that the versions Pino lists now work for you?  If so it is the same bug.
Comment 4 Gerald Cox 2009-01-13 02:20:06 UTC 
Yes, I receive a blank advanced settings page when I select Print / Properties / Advanced.
Comment 5 John Layt 2009-01-13 20:08:40 UTC 
Now fixed upstream for forthcoming Qt 4.5.0, but also bypassed in forthcoming KDE 4.2 and KDE 4.1.4 releases.

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