Created attachment 49274 [details] Broken PDF A/1 To reproduce: * Write something in your document (or don't) * Click "File" > "Export as PDF..." * Check "PDF A/1-a" on the first tab * Click "Export" * Try opening with Adobe Reader (I'm using version 9). * Let Reader tell you your document has an "invalid color space" This bug can be very embarrassing, I, for instance, mostly use Evince which shows the document fine, but sent this document to someone using Adobe Reader which of course wouldn't open it. This seems to happen in all LibreOffice application.
* Not reproducible under Windows (32-bit) with any LibreOffice version * Not reproducible under Ubuntu (64-bit) with LibreOffice 3.3.3 * Reproducible under Ubuntu (64-bit) with LibreOffice 3.4.1 Can anyone with Mac OS or 32-bit Linux please check?
Not reproducible on Ubuntu 11.04, LibreOffice 3.3.3 OOO330m19 (Build:301), German UI, Intel 32-bit
Testing again with 3.4.2rc2 on Ubuntu, 32-bit. Here, I cannot confirm this bug when following Aaron's description. As this seems to be 64-bit related, can anyone test this bug with a 64-bit Linux and LibreOffice 3.4.x? Thanks.
I can reproduce this bug on LibreOffice 3.4.2 / Gentoo 64bit
I can reproduce it too, Kubuntu 11.04, 64-Bit. I´m not using the LO-Version shipped with Kubuntu. I removed this and downloaded the DEB-installation files. The PDF fails to open only in Acrobat Reader - Okular, e.g., works fine. I receive the error message "Falscher Farbraum" what means wrong color space.
Hi Everyone, may be this issue is related to this old one https://bugzilla.novell.com/show_bug.cgi?id=467181 whose title was "PDF/A export broken - Adobe Acrobat reports Invalid ColorSpace" and the fix would be the same because it's a new regression? Hope that help, Carlo
I have just tested on: - linux updated OpenSuse 11.2, kernel 2.6.38.6, x86-64; - LibreOffice, vanilla, 3.4.3 (rc2/final), rpm, x86-64; - export an odt file to pdf/A-1a; - well opened on Evince 2.30.3, document viewer, use poppler/cairo (0.12.3); - not opened with "Invalid color space" on Adobe Acrobat Reader 10.1.0, win32, ita guied, on Windows Vista, ita guied, SP2, 64 bit (x86-64). Have a nice day, Carlo
NOT reproducible with own sample and "LibreOffice 3.4.3 RC2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:302)]". My samples open fine with AR X. Seems to be Linux (64bit) specific. I can confirm the effect with reporter's PDF sample, but without source document it's useless. Indeed, might be <https://bugzilla.novell.com/show_bug.cgi?id=467181> has come back, but that's not sure. I believe eit's CONFIRMED by several users @Aaron Strontsman: Please contribute complete information concerning your PDF settings and contribute a text kit (all files zipped into it ) with - source.odt (as simple as possible) - exportresult.PDF That might ease debugging very much. Do you also see the problem for exports from CALC and DRAW?
Created attachment 50803 [details] Original LibreOffice writer and calc files, with faulty A/1-a PDF File saved in LibreOffice 3.4.2 OOO340m1 (Build:203) Ubuntu linux 64 bit 11.04
Thank you, that was quick. <http://www.pdf-tools.com> rated LibreOffice3_4_2_340_203_UbuntuLinux64bitmy.pdf as ok, but I can't tell whether it's reliable. For the one woh needs A/1 this really is a blocker, but I believe only very few users need that option, so only "Major". I do not see this one blocking Bug 35673
@Lubos: Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
@Rainer: * you're (most probably) using 32-bit LibO (on a 64-bit OS) -- so you don't see the bug * the minimal test case is an empty document (@Guillaume: thanks) * it happens after deleting LibO profile in vanilla LibO @Carlos: Thanks a lot.
Aaron Strontsman: Arghh, yes! We still do not have a convention that we WIN users using "Builds off the peg" understand. It would be great if you could leave a hint on <http://wiki.documentfoundation.org/QA-FAQ#Bugzilla_HowTos> how to mark "LibO 64 bit builds" unitary and different from "64bit-OS". May be "64bit-build" in the subject line or similar?
(In reply to comment #6) > may be this issue is related to this old one > https://bugzilla.novell.com/show_bug.cgi?id=467181 > whose title was "PDF/A export broken - Adobe Acrobat reports Invalid > ColorSpace" and the fix would be the same because it's a new regression? This seems spot on; most of the patch introduced as part of the resolution of the bug you link to is inactivated (detected as trailing garbage by patch), because a new hunk was inserted incorrectly (stealing this hunk's " ***************" marker), in commit cf6aa9b361479a482898d0728f6849953f25c6be Author: Tor Lillqvist <tlillqvist@novell.com> Date: Mon Jan 24 01:19:29 2011 +0200 Use MSVC settings not just on x86 (in core) I'm working on it, will commit shortly (after test).
On 2011-07-18 15:18:50 PDT Aaron Strontsman asked: "Can anyone with Mac OS or 32-bit Linux please check?" ANSWER: Not reproducible under Mac OSX 10.6.8 with LibO-dev 3.5.0 Build ID: eefb4c7-f2188a3-4eb4f62-09af278 and Acrobat Pro 9.4.5
Fixed (again) in master branch (to become 3.5); backport of fix to 3.4 (to be included in 3.4.4) requested.
Great work! Thank you very much! Carlo
The fix is now also committed to 3.4 branch; the fix will be in 3.4.4
*** Bug 38347 has been marked as a duplicate of this bug. ***
As 3.4.4 is releasing, closing this bug
As 3.4.4 is released, closing this bug.
Bug opened again. On Linux Mint 13 KDE 64 bit and LibreOffice from PPA, version 3.6.0.2 Broken PDF A/1 To reproduce: * Create a document in Writer * Click "File" > "Export as PDF..." * Check "PDF A/1-a" on the first tab * Click "Export" * Try opening with Adobe Reader (I'm using version 9). * Using any validating tool (as http://www.validatepdfa.com/en/online.htm ) you will get an "invalid color profile" error.
@Fridrich: this bug was corrected by the "use typedefs and endianess from sal" patch hunk from icc/SampleICC-1.3.2.patch Since you removed that file, I'm going to blindly reassign to you. Please take a look. See commits: 3b32204d9f900130cd1877675d8b51281b81f90d 9e635f111dad04be717913100cdaf2de4112a245 and https://bugzilla.novell.com/show_bug.cgi?id=467181
My main problem is that I am unable to reproduce the problem on my 64-bit system with LO master build or 3.6.1 release :( The change in which I removed the icc module was just removing a duplicate functinality. Some modules of LibreOffice use liblcms2 for colour management and the library can generate just fine a sRGB profile. I generate it using that library (which has no know endianess issues) and push it byte by byte into the PDF file. I tried to follow with the above mentioned steps, but for me acrobat reader 9.5.1 on Linux opens the file just fine and indicates to the user that it is viewed in PDF/A mode. I don't mind to fix the issue if other people have it, but I would really need some help in determining where the problem actually lies.
(In reply to comment #24) > My main problem is that I am unable to reproduce the problem on my 64-bit > system with LO master build or 3.6.1 release :( > I tried to follow with the above mentioned steps, but for me acrobat reader > 9.5.1 on Linux opens the file just fine and indicates to the user that it is > viewed in PDF/A mode. Indeed, Adobe Acrobat Reader does not complain, but it does not validate the file any more than it needs to display it. Validators *do* complain. The new problem is different than the one in this bug, and probably not 64bit-specific. Opened bug 54546 to track the new problem, and closing this one again.