Bug 35180

Summary:	objects with invisible line style and hatched area fill may not export to pdf
Product:	LibreOffice	Reporter:	Joe Smith <jes>
Component:	Drawing	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium	CC:	fyvaao
Version:	3.3.1 release
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	34272
Bug Blocks:	37247
Attachments:	Sample document showing problem

Description Joe Smith 2011-03-10 09:54:39 UTC

Created attachment 44309 [details]
Sample document showing problem

Testing LibO 3.3.1 on Fedora Linux 13

Also reported as http://openoffice.org/bugzilla/show_bug.cgi?id=117223

Objects that combine a hatched area fill and line style "invisible" may not be
exported properly to pdf.

Steps to reproduce:

1) Open the attached test document
2) Export to pdf

See that in the exported pdf, only object "A" is exported properly. Object "B",
which also has a hatched area fill, is not filled in the exported pdf; only its
label is visible.

3) Change the object's line style (Format > Line > Line > Style: "Continuous")
to anything other than "invisible"; export to pdf

In this case, both objects are exported correctly.

4) Reload the original document
5) Copy object "A" to the clipboard, then delete object "A"
6) Paste the copy of object "A"
7) Export to pdf

Now object "B" is exported correctly, where the copy of object "A" is not. The
order in which the hatched objects are exported seems to be significant.

Comment 1 Björn Michaelsen 2011-12-23 11:50:55 UTC

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html

Comment 2 Florian Reisinger 2012-08-14 14:02:56 UTC

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian

Comment 3 Florian Reisinger 2012-08-14 14:03:52 UTC

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian

Comment 4 Florian Reisinger 2012-08-14 14:08:26 UTC

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian

Comment 5 Florian Reisinger 2012-08-14 14:10:29 UTC

Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.