Summary: | PDF not rendered correctly | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | ayr035+kde |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | CC: | aacid |
Priority: | NOR | ||
Version: | 0.17.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Okular incorrect page sizes
Incorrect rendering of a page QPDFView rendering of page (correct rendering) Sample PDF that exhibits the bug |
Description
ayr035+kde
2013-08-21 00:09:28 UTC
Created attachment 81824 [details]
Okular incorrect page sizes
Created attachment 81825 [details]
Incorrect rendering of a page
Created attachment 81826 [details]
QPDFView rendering of page (correct rendering)
Created attachment 81827 [details]
Sample PDF that exhibits the bug
Are you using the 'trim margins' feature? Trim margins was enabled. I was not even aware that "Trim Margins" was a feature in Okular. I have no idea how it got enabled. I had gone through every setting I could find under the settings menu (I expected to see something under the General tab in Okular Settings). This is weird, three things: * Can you confirm that without trim margins everything looks fine? * Are you a "new" user of okular or you've been using it for a long time? We did some settings splitting that may have caused this if you installed okular 4.10 before you installed kdelibs 4.10 * Can you create a new blank user and see if the option is enabled for you? (I just did it and is not, but let's confirm what happens for you) If you can provide the information requested in comment #7, please add it. Sorry for the long delay. * Without trim margins, it looks as expected. * I use okular pretty exclusively. No other pdf reader has the speed/features that okular has. * I just created a new user, it is off by default. Maybe I just hit the magic key accelerators that turn it on without me being aware (Alt+V > T). I still don't remember consciously enabling it though. Anyway, I'm glad it was a simple solution. Thanks for your research :-) |