After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 486957 - pdf form not fillable, check boxes rendered incorrectly
pdf form not fillable, check boxes rendered incorrectly
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: PDF
2.20.x
Other All
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-15 21:16 UTC by Greg Grossmeier
Modified: 2007-10-16 13:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Greg Grossmeier 2007-10-15 21:16:55 UTC 
Please describe the problem:
Can not fill in text fields nor check boxes in a pdf form that allows this.  The check boxes also render incorrectly. 

Steps to reproduce:
1. Open the document
2. Try to enter text/mark a checkbox
3. 


Actual results:
Nothing, unable to enter text/mark the checkbox

Expected results:
Ability to enter text/mark the checkbox.

Does this happen every time?
Only certain documents, not all forms.

Other information:
Link to problem causing pdf:
http://www.cseced.org/jobs/images/application%20teacher%20specialist.pdf
Comment 1 Greg Grossmeier 2007-10-15 21:17:34 UTC 
Bug in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/152967
Comment 2 Greg Grossmeier 2007-10-15 21:24:41 UTC 
The problem causing pdf has these properties:
Creater: Adobe Designer 7
Producer: Adobe Designer 7
Format: PDF-1.6
Optimized: No

Another pdf from the same site ( http://www.cseced.org/jobs/images/Application%20for%20Administrative%20Position.pdf )
This one works as expected (can fill out the form and check boxes correctly)
Creator: Acrobat PDFMaker 7.0.7 for Word
Producer: Acrobat Distiller 7.0.5 (Windows)
Format: PDF-1.6
Optimized: Yes
Comment 3 Carlos Garcia Campos 2007-10-16 13:29:54 UTC 
Thanks for the bug report. It's a poppler bug. I've just fixed it in git (poppler-0.6 and master branches)