Bug 179426 - okular misrenders (badly) PDF forms
Summary: okular misrenders (badly) PDF forms
Status: RESOLVED UPSTREAM
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 23:19 UTC by doc.evans
Modified: 2009-01-03 00:36 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description doc.evans 2009-01-02 23:19:50 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

I received a PDF form from an attorney. The form contains checkboxes, and okular represents different checkboxes as being checked than Acrobat Reader does. Acrobat Reader's interpretation is correct.

In other words, some checkboxes are rendered by okular as being checked when in fact they are not checked, and vice versa.

I don't think that I really need to point out that this bug can have terrible consequences if the form being rendered is from an attorney or accountant.

I have tried to extract a single page that does not contain personal information (so I could attach it here) but have not been able to do so.
Comment 1 Pino Toscano 2009-01-02 23:27:01 UTC
Which results do you get if you open the document with Evince?
Comment 2 doc.evans 2009-01-03 00:04:41 UTC
quickly installs evince and...

the same result as okular.


Comment 3 Pino Toscano 2009-01-03 00:12:55 UTC
As I suspected... it is a bug of the Poppler library.
I believe it is already reported for Poppler, but in case it is not, please report it in the Poppler bug tracker, https://poppler.freedesktop.org, "poppler" product.

Thanks!
Comment 4 doc.evans 2009-01-03 00:36:32 UTC
Thank you. I've filed it as a comment on a pre-existing bug there: https://bugs.freedesktop.org/show_bug.cgi?id=19359. 

I'm not certain that this is the same bug as that one, but it seems at least plausible.