Description: When attaching a specific pdf document printed by Microsoft pdf printer, then exporting to pdf again, opening the doc with Acrobat Reader XI (ver 11.0.23), says: "An error exists on this page. Acrobat may not display the page correctly. Please contact the person who created the PDF document to correct the problem". Steps to Reproduce: 1.Create an empty odt document [bugtest.odt] 2.Add some text 2.Print the odt with microsoft pdf printer [print to file:printed.pdf] 3.Import the printed pdf [file:printed.pdf] 4.Export the odt to pdf using File->Export menu [export to file:bugtest.pdf]. 5.Open the final print [file:bugtest.pdf] with a viewer, in my case Acrobat Reader XI 6.Watch it fail Actual Results: The message "An error exists on this page. Acrobat may not display the page correctly. Please contact the person who created the PDF document to correct the problem" appears in a box. The written text is visible. Expected Results: Either (preferred order): A-The included pdf documents is also displayed in the exported pdf. B-Writer would refuse to attach the pdf if there is a good reason. C-Write a message during export explaining that this is not possible because of <reason> D-Remove the pdf export feature? Windows will always have a pdf printer? Reproducible: Always User Profile Reset: No Additional Info: Workaround:Print the document with Microsoft pdf printer works. It is only the export that fails.
Hi there, thank you for reporting the bug. I can't seem to reproduce the bug, I opened the viewer via Adobe Acrobat and seem to have no issues opening the PDF. Perhaps I followed the print instructions wrong, could you add an attachment of bugtest.pdf in question? Setting to NEEDINFO for now.
Created attachment 193585 [details] Final output of the test
Created attachment 193586 [details] Printed with Microsft pdf printer before attaching
Let me add; I imported the pdf by drag and drop.
[Automated Action] NeedInfo-To-Unconfirmed
Let me also add; safari on my iphone seems to be able to view the attached pdf. Could this be an Acrobat Reader XI bug?