[Upstream] pdf export with pdf/a-1a creates problematic pdf

[Fritz Heinrichmeyer]

libreoffice-3.4.3, oneiric amd64:

Exported pdf files cannot be opened with acroread, they work with evince.

This bug is malicious as currently only non oneiric computer users cannot open/view my pdf files. There is no acroread now in oneiric amd64. This error only occurs when pdf/a-1a is selected on export in libreoffice. This error is not present in libreoffice 3.4.3 on windows. I selected this option as i had strange looking spacing with standard helvetica fonts (maybe another bug, but for now this is more important).

[Stefan K. (astron)]

Created attachment 49274
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.

[Stefan K. (astron)]

* 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?

[GT (gleppert)]

Not reproducible on Ubuntu 11.04, LibreOffice 3.3.3 OOO330m19 (Build:301), German UI, Intel 32-bit

[GT (gleppert)]

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.

[Bug-report (bug-report)]

I can reproduce this bug on LibreOffice 3.4.2 / Gentoo 64bit

[Spam4sven (spam4sven)]

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.

[Carlo-strata (carlo-strata)]

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

[Carlo-strata (carlo-strata)]

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

[Libreoffice-z (libreoffice-z)]

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?

[billjoie (joie-bill)]

Created attachment 50803
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

[Libreoffice-z (libreoffice-z)]

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

[Libreoffice-z (libreoffice-z)]

@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.

[Stefan K. (astron)]

@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.

[Libreoffice-z (libreoffice-z)]

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?

[Lionel Elie Mamane (lionel-mamane)]

(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 <email address hidden>
 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).

[Rk601 (rk601)]

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

[Lionel Elie Mamane (lionel-mamane)]

Fixed (again) in master branch (to become 3.5); backport of fix to 3.4 (to be included in 3.4.4) requested.

[Carlo-strata (carlo-strata)]

Great work! Thank you very much!

Carlo

[Lionel Elie Mamane (lionel-mamane)]

The fix is now also committed to 3.4 branch; the fix will be in 3.4.4

[penalvch (penalvch)]

Fritz Heinrichmeyer, thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Björn Michaelsen (bjoern-michaelsen)]

Fix commited:

http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=927c1ed3d8ce670fb681563c3cf4ea94abe62a36

[Björn Michaelsen (bjoern-michaelsen)]

will be released with 3.4.3-1ubuntu3

[Björn Michaelsen (bjoern-michaelsen)]

3.4.3-1ubuntu3 is released in oneiric.

[rpr nospam (rpr-nospam)]

*** Bug 38347 has been marked as a duplicate of this bug. ***

[Lionel Elie Mamane (lionel-mamane)]

As 3.4.4 is releasing, closing this bug

[Lionel Elie Mamane (lionel-mamane)]

As 3.4.4 is released, closing this bug.

[Alz (albertozugno)]

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.

[Lionel Elie Mamane (lionel-mamane)]

@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