Bug 52145 - PDF: wrong drawing of circle with gradient when drawing resized
Summary: PDF: wrong drawing of circle with gradient when drawing resized
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.0.1 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-16 09:51 UTC by S K
Modified: 2015-06-15 17:11 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
odt file, when exported to PDF the bug is shown (15.37 KB, application/vnd.oasis.opendocument.text)
2012-07-16 09:51 UTC, S K
Details
faulty PDF file (4.85 KB, application/pdf)
2012-07-16 09:52 UTC, S K
Details
faulty doc file (272.50 KB, application/msword)
2012-07-16 10:03 UTC, S K
Details
faulty pdf file created from doc file (281.89 KB, application/pdf)
2012-07-16 10:05 UTC, S K
Details
Document created with linux, modified in windows (24.37 KB, application/vnd.oasis.opendocument.text)
2012-12-18 12:15 UTC, ydutrieux
Details

Note You need to log in before you can comment on or make changes to this bug.
Description S K 2012-07-16 09:51:03 UTC
Created attachment 64264 [details]
odt file, when exported to PDF the bug is shown

Problem description: 
This problem is hard to reproduce. Please use the attached odt file to reproduce it. 

Steps to reproduce:
1. Insert drawing
2. Draw rectangle circle
3. Set gradient to circle
4. Resize drawing as a picture
5. Export to PDF

Current behavior:
Wrong drawing of circle. Strange rectangular is shown.

Expected behavior:
Circle should be drawn.

Platform (if different from the browser): 
              
Windows XP
Comment 1 S K 2012-07-16 09:52:06 UTC
Created attachment 64265 [details]
faulty PDF file
Comment 2 S K 2012-07-16 10:03:04 UTC
Created attachment 64266 [details]
faulty doc file
Comment 3 S K 2012-07-16 10:05:20 UTC
Created attachment 64267 [details]
faulty pdf file created from doc file
Comment 4 S K 2012-07-16 10:08:37 UTC
Observer on LibreOffice 3.5.4  (linux).

1. Open writer
2. Create drawing
3. Draw rectangular circle with the gradient
4. Save file as doc (see Untitled 1.doc)
5. Close writer
6. Open doc file
7. Export as PDF (see Untitled 1.pdf)

Seems like preview of OLE makes the problems when used with PDF export.
Comment 5 ydutrieux 2012-12-18 12:15:35 UTC
Created attachment 71723 [details]
Document created with linux, modified in windows

CONFIRMED on libo4 Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Win7 - 32bits

CONFIRMED on libo4 Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Ubuntu 12.04 64bits
ONLY IF DOCUMENT has been CREATED in WINDOWS.

Step to reproduce (not exactly yours) : 
- Insert - Objet - OLE - Libo Drawing
    Draw a circle with button "Basic Shapes" of Drawing toolbar
    <right-clic on it>- Area - <Gradients tabs> - OK
- <clic on writer document to go outside OLE object>
- Clic on pdf icons to generate PDF.
<if the bug doesn't appear, resize the object a little>
then export PDF.

nb: if the circle is draw driectly with toolbar (without OLE Object), it's ok.

Here joined document created with Linux (first OLE) and after I have inserted a second OLE with Windows. it was ok until I resize it.
Comment 6 Jorendc 2013-01-26 22:37:32 UTC
(In reply to comment #5)
> Created attachment 71723 [details]
> Document created with linux, modified in windows
> 
> CONFIRMED on libo4 Version 4.0.0.0.beta1 (Build ID:
> 87906242e87d3ddb2ba9827818f2d1416d80cc7)
> Win7 - 32bits
> 
> CONFIRMED on libo4 Version 4.0.0.0.beta1 (Build ID:
> 87906242e87d3ddb2ba9827818f2d1416d80cc7)
> Ubuntu 12.04 64bits
> ONLY IF DOCUMENT has been CREATED in WINDOWS.

Therefore I mark this bug as NEW.
Following the flowchart [1] I set/(leave it by it's defaults) priority to 'Normal' 'Medium'.
Comment 7 QA Administrators 2015-04-19 03:23:02 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   *Update the version field
   *Reply via email (please reply directly on the bug tracker)
   *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 
3. Leave a comment with your results. 
4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Comment 8 Gordo 2015-06-15 17:11:10 UTC
Could not reproduce.

Windows Vista 64
Version: 4.4.4.2
Build ID: f784c932ccfd756d01b70b6bb5e09ff62e1b3285

4.2.8.2

Bug present in 4.1.6.2.

Changed to RESOLVED WORKSFORME.