Created attachment 55501 [details] Problem PDF Example PDF made by save as from Inkscape. Looks fine in PDF viewers. In LODraw the gradient/pattern extends to the limits of the image. 3.5.0b2 does exactly the same thing. This is a specific issue extracted from bug 43806
Created attachment 55502 [details] source SVG for the problem PDF
Created attachment 55503 [details] Screen shot of LODraw after opening the problem PDF
Problem is unchanged in 3.5.0rc1 on Windows
Reproduced with LOdev 3.5.0beta3 e40af8c-10029e3-615e522-88673a2-727f724 Ubuntu 10.04.3 x86 Linux 2.6.32-37-generic Russian UI
Confirmed:4.2.0.2:OSX OS > All
Created attachment 98038 [details] New gradient test (PDF) Two types of bugs are mixed in provided test PDF (gradient.pdf): clipping and opacity. Here is the new test files: gradient_test4.svg and gradient_test4.pdf They are free from opacity bugs (and from big black rectangles as well).
Created attachment 98039 [details] New gradient test (SVG)
Created attachment 98040 [details] Clipping patch (experimental) Clipping must be performed without modifying of source objects. But there is no such feature in LibreOffice Draw. I have tried to implement modifying clipping. But I was faced with two problems: 1. Radial gradients rendered by poppler as 256 polygons with 400 points. That is bad for performance, but when clip is applied, situation becomes even worse. 2. Function basegfx::tools::clipPolyPolygonOnPolyPolygon() behaves badly in border cases. With my test file it fails 2 times: with radial gradient clipping and with pattern fill clipping. Here is my experimental patch file. Maybe it will be useful for someone.
Bug 86211 contains newer version of clipping patch
Confirmed: 4.4.3.2: Linux IA64 Black area shouldn't show up.
Removing comma from Whiteboard (please use a space to delimit values in this field) https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard#Getting_Started
Confirmed Version: 5.2.0.0.alpha0+ Build ID: 6b232aeecc55f1715bc111e636e36a8e24827efb CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-01-26_07:40:04 Locale: de-DE (de_DE)
*** Bug 54924 has been marked as a duplicate of this bug. ***
Is it really PDF import to LO Draw or may be PDF export? Could somebody please explain the bug step by step as in Bug 54924 which has been marked as duplicate?
(In reply to kitaets from comment #14) > Is it really PDF import to LO Draw or may be PDF export? When I create a rectangle in Draw, fill it with a gradient from black to white, export to pdf and reopen the pdf, the object is rasterized (same as for svg in tdf#64464). Looking into the raw pdf file there is nothing obviously wrong. I'm not saying the export filter has no bugs, but do we really need two tickets? Having a large list to go through might be discouraging. Anyway, feel free to reactivate the duplicate if you think it's necessary (in this case set blocks 99746 and see as well 44731 please).
Created attachment 135945 [details] test 4 in LOO 5.4.0.3 64 bit same in 5.3.5.2 white sheet, right circles, wrong lines outside the circles
problem pdf black sheet in windows 10 64bit Version: 5.4.0.3 (x64) Build-ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL and Version: 5.3.5.2 (x64) Build-ID: 50d9bf2b0a79cdb85a3814b592608037a682059d CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Layout Engine: new; Gebietsschema: de-DE (de_DE); Calc: group
Created attachment 135946 [details] gradient-svg test LOO-5.4.0.3-64bit problem in last circle gradient
test in 5.4.0.3 wrong direction of second gradient third gradient not white near circle line. 4th circle is black full inside and a greater rectangle black in addition
Created attachment 135948 [details] gradient-svg-inkscape-0.92.2-64bit screenshot 4th circle gradient with more lines in inkscape 0.92.2
Created attachment 135949 [details] source svg in firefox 52.3 screenshot less lines in 4th circle.
Comment on attachment 135948 [details] gradient-svg-inkscape-0.92.2-64bit screenshot more lines in 4th circle not reproducable
Created attachment 135951 [details] gradient-svg-scribus-1.5.3-64bit-test screenshot scribus 1.5.3 also with problem in 4th circle by gradient.svg
Created attachment 135952 [details] gradient-test4-acrobatreader-screenshot more lines in 4th circle
Created attachment 135953 [details] gradient-pdf-acrobatreader-screenshot all right like svg
Created attachment 135954 [details] gradient-svg-inkscape-0.92.2-64bit-test2 all right like svg in Firefox
Comment on attachment 135949 [details] source svg in firefox 52.3 screenshot all ok, not less or more lines
5.4.3.2 64 bit win10 same like 5.4.0.3, no improvement or change.
in LO Draw 6.1 beta 2 Problem PDF opens with black background and wrong gradients but Source SVG from Problem PDF opens very fine still repro
For 6.2 the pdfium based filter is now handling both import and insert, and the pdfium rendering to bitmap on canvas correctly renders the linear, radial and pattern fills of attachment 55501 [details] or attachment 98038 [details] But break of the inserted PDF, or Import (e.g. opening) of the PDF with PDFium, is not handling clip of the gradient fills well. Should this and similar import/break bugs be closed and restated against the new PDFium filter? @Miklos, Ashod, Kendy
I would let Ashod / Kendy decide when the pdfium import is ready to replace the poppler one.
svg import improved but not perfect in LO 6.1.0.3 black circles incomplete. pdf-import same buggy like before.
blue circles incomplete not black
svg import in 6.3.0.4 circles are incomplete, but in export pdf all is ok. so nearly 50% is here ok. import of problem pdfs are nearly like bugs 43806 and 44729
Created attachment 153612 [details] import gradient.svg in Lo 6.3.0.4 and export pdf svg import to LO 6.3.0.4 circles are incomplete. but pdf export the circles are ok and the result is perfect in my view. so svg import with pdf export is ok. problem pdf import failed like before in 5.x and 6.x
Dear mathog, 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 https://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
Always here with LibO 7.2.7.2 x64 and 7.3.5.2 x86, both on Win 11 Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 12; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL Version: 7.3.5.2 (x86) / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 12; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL I change Hardware -> All
FYI this is separate from the 113050 bug I just fixed.