Created attachment 142558 [details] How the PDF looks in 6.1 Steps to reproduce: 1. Open attachment 111685 [details] from bug 87967 2. Export to .PDF -> the green gradient is not exported to PDF Reproduced in Version: 6.1.0.0.beta1+ Build ID: 8b96445766efe237eb47608ade6c147673466e2e CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group [Bug found by office-interoperability-tools]
Regression introduced by: author Armin Le Grand <Armin.Le.Grand@cib.de> 2017-10-30 16:29:09 +0100 committer Armin Le Grand <Armin.Le.Grand@cib.de> 2018-04-17 02:05:57 +0200 commit 7f9b0f47979dcb7abfed37bb7cd38ab51eac6011 (patch) tree 639b6289605dc4b108b70d2da56dd214e62a5be1 parent 0f93692fda4226323422cf82ce34ae4bd5e22fab (diff) tdf#113197 Add MaskPrimitive (clip) to EMF/WMF if needed Added code to quartz vcl implementation that takes care when BitmapPalette.count != (depth^^2)-1 - which may be the case anytime. If then a bitmap value exists that goes beyond that count, a invalid access was executed Bisected with: bibisect-linux64-6.1 Adding Cc: to Armin Le Grand
It seems that this document has PPT document inside. The root cause of the issue is this part of code, which breaking clipping target region: const basegfx::B2DRange aMtfRange(aMtfTarget.Left(), aMtfTarget.Top(), aMtfTarget.Right(), aMtfTarget.Bottom()); // tdf#113197 get content range and check if we have an overlap with // defined target range (aMtfRange) if (!aMtfRange.isEmpty()) { const basegfx::B2DRange aContentRange(xRetval.getB2DRange(rViewInformation)); // also test equal since isInside gives also true for equal if (!aMtfRange.equal(aContentRange) && !aMtfRange.isInside(aContentRange)) { // contentRange is partly larger than aMtfRange (stuff sticks // outside), clipping is needed const drawinglayer::primitive2d::Primitive2DReference xMask( new drawinglayer::primitive2d::MaskPrimitive2D( basegfx::B2DPolyPolygon( basegfx::utils::createPolygonFromRect( aMtfRange)), xRetval)); xRetval = drawinglayer::primitive2d::Primitive2DContainer{ xMask }; } }
Dear Xisco Faulí, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This issue was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=a4c46ceec433edf0c5de03ea8d36857a455cafd2 Kudos to Regina