Other libraries are whatever's in the current Ubuntu 8.10 (Intrepid) distribution.
Loading, editing a form field in, then saving the affected PDF still results in a zero-byte file, with no errors reported on the command line or via the GUI.
Oddly enough, this version of evince is supposed to deal with this situation from that end; see GNOME bug 566791, which was about the same problem, and this revision, which was included in the tested version:
Is the above setup working for anyone? I may be testing it wrong, but I don't think so; I'm quite sure that my testing copy of evince is linked to my testing copy of the poppler libs, and so on.
Is there any further debugging or tracing that I could do that might be of some help?
I tested the following setup (all checkouts were the current version as of about yesterday):
cairo eb2a73ba6d29049 7cabb0f917c0375 eea919178e (1.9.1 series) eadb92023b27e68 f402e38dd0 + Carlos's patch
poppler 26a8217160c1eae
evince r3496
Other libraries are whatever's in the current Ubuntu 8.10 (Intrepid) distribution.
Loading, editing a form field in, then saving the affected PDF still results in a zero-byte file, with no errors reported on the command line or via the GUI.
Oddly enough, this version of evince is supposed to deal with this situation from that end; see GNOME bug 566791, which was about the same problem, and this revision, which was included in the tested version:
http:// svn.gnome. org/viewvc/ evince? view=revision& revision= 3493
Is the above setup working for anyone? I may be testing it wrong, but I don't think so; I'm quite sure that my testing copy of evince is linked to my testing copy of the poppler libs, and so on.
Is there any further debugging or tracing that I could do that might be of some help?