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 695615 - evince does not save filled PDF forms
evince does not save filled PDF forms
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: PDF
3.6.x
Other Linux
: Normal critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-11 09:47 UTC by Till Kamppeter
Modified: 2018-05-22 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
V0100.pdf (324.09 KB, application/pdf)
2013-03-11 09:47 UTC, Till Kamppeter
Details

Description Till Kamppeter 2013-03-11 09:47:39 UTC
Created attachment 238567 [details]
V0100.pdf

Also reported as Ubuntu bug:

https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1153517

I am on Raring and open the attached PDF file with a form. I can fill in the form without problems, but if I want to save the form (there is only "Save a copy ..." not "Save" for simply saving back the form content) I get the error message

The file could not be saved as "...".
Document is encrypted

The issuer of the form has explicitly allowed to save the filled form. Adobe Reader on 32-bit Precise saves it without problems and with the filled fields (and I can load the saved form with evince on my Raring box and print it with the filled data).
Comment 1 José Aliste 2013-03-26 13:34:49 UTC
Which version of poppler are you using? I believe that this bug was a poppler one that is already fixed as of poppler 0.22
Comment 2 Till Kamppeter 2013-03-26 17:16:41 UTC
I am on Ubuntu Raring, it is still on 0.20.5.
Comment 3 Till Kamppeter 2013-03-26 17:19:35 UTC
Can you attach a patch to backport the fix into Poppler 0.20.5? Thanks.
Comment 4 José Aliste 2013-03-26 18:50:54 UTC
I am sorry, but I don't know when or with which commit(patch) this was fixed... I just happened to test a related bug and realized that the bug was  no-longer valid. There are a lot of bugfixes in poppler-0.22, so I would recommend trying a newer poppler, instead of just bisecting and trying to apply a patch. Unfortunately, Ubuntu takes a lot of time to update their poppler packages.
Comment 5 Germán Poo-Caamaño 2013-03-26 19:08:18 UTC
Ubuntu is going to ship 0.20 for Raring.  One alternative would be filing a bug in launchpad requesting to ship poppler 0.22 (tough, Ubuntu is in release freeze, AFAIK) *and* an Ubuntu developer that sponsor that request.
Comment 6 Gökcen Eraslan 2013-05-06 11:07:56 UTC
Git bisect reveals this commit[1]:

commit 800b2e37d3c4c73147bf9e11d9f38afe2183ab9d
Author: Fabio D'Urso <fabiodurso@hotmail.it>
Date:   Wed Aug 1 14:07:10 2012 +0200

    Initial support for saving encrypted documents
    
    - Do not refuse to save encrypted documents
    - Copy the /Encrypt value in the new document's trailer dictionary
    - Mark indirect objects referred from /Encrypt as not encrypted in XRef::scanSpecialFlags


[1] http://cgit.freedesktop.org/poppler/poppler/commit/?id=800b2e37d3c4c73147bf9e11d9f38afe2183ab9d
Comment 7 Germán Poo-Caamaño 2013-05-06 16:01:52 UTC
This should be requested in poppler's bugzilla.

Leaving this bug opened in the meanwhile.  Once reported there, this should be closed as NOTGNOME with a link to the poppler bug (in "See Also" field).
Comment 8 GNOME Infrastructure Team 2018-05-22 15:00:37 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/332.