Bug 732543 - Form data saved with Evince not readable with PDF Reader X
Summary: Form data saved with Evince not readable with PDF Reader X
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 2
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-22 20:38 UTC by Derek Seabrooke
Modified: 2011-11-09 20:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 20:06:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Form filled in using Evince (520.26 KB, application/pdf)
2011-08-22 20:38 UTC, Derek Seabrooke 		no flags Details
original unfilled form (484.78 KB, application/pdf)
2011-08-22 20:40 UTC, Derek Seabrooke 		no flags Details
View All

Description Derek Seabrooke 2011-08-22 20:38:31 UTC 
Created attachment 519348 [details]
Form filled in using Evince

Description of problem:

When PDF file with fillable forms is completed and saved, the data does not show up when opened in PDF Reader X


Version-Release number of selected component (if applicable):

2.32.0


How reproducible:

very


Steps to Reproduce:
1.  Open attached form in evince
2.  Open same form in PDF Reader X
  
Actual results:

PDF Reader X shows forms blank

Expected results:

PDF Reader X show data filled with Evince
Comment 1 Derek Seabrooke 2011-08-22 20:40:11 UTC 
Created attachment 519349 [details]
original unfilled form
Comment 2 John Poelstra 2011-11-09 20:06:31 UTC 
    Thank you for your bug report. 

    We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from: 

    http://fedoraproject.org/get-fedora
Note You need to log in before you can comment on or make changes to this bug.