Bug 47837

Summary: PRINTING: Print problem with copped images in association with fontwork
Product: LibreOffice Reporter: François Guerraz <kubrick>
Component: DrawAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: sasha.libreoffice
Priority: medium    
Version: 3.5.1 release   
Hardware: Other   
OS: All   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Try printing this document and you'll notice that what you see is not really what you get...
What you see in the editor
What you get on the printer

Description François Guerraz 2012-03-25 04:14:15 UTC
Created attachment 58999 [details]
Try printing this document and you'll notice that what you see is not really what you get...

Problem description: 

Steps to reproduce:
1. Insert an image from a file
2. Crop the image and move it to its place
3. Insert a fontwork text on top of it
4. Print the image

Current behavior:
The image is not cropped properly and you can see the original edges of the cropped image

Expected behavior:
The image should be cropped properly.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20100101 Firefox/11.0
Comment 1 François Guerraz 2012-03-25 04:17:50 UTC
Created attachment 59000 [details]
What you see in the editor
Comment 2 François Guerraz 2012-03-25 04:19:05 UTC
Created attachment 59001 [details]
What you get on the printer
Comment 3 François Guerraz 2012-04-23 07:53:21 UTC
Is there anything else I can say or do to help you progress on this bug, it's been a month now and no updates on that bug.

Cheers.
Comment 4 sasha.libreoffice 2012-06-18 06:03:44 UTC
Thanks for bugreport
Please, verify if in last version of LibreOffice still reproducible
(3.5.4 or more new)
Comment 5 François Guerraz 2012-06-27 02:03:12 UTC
Hi,

Bug fixed in 3.5.4.

Just by sheer curiosity, can you point me at the commit that fixed the problem?

Cheers,

François.
Comment 6 sasha.libreoffice 2012-06-27 02:07:58 UTC
> Just by sheer curiosity, can you point me at the commit that fixed the problem?
No. This happened completely accidentally. Nobody know this.