Description: FILEOPEN: this input file is a pdf that contains a watermark. opening file in pdf reader shows the same as a light watermark behind the text. opening the file in draw shows the watermark as a full opaque image infront of text rendering entire file unusable. only option is to delete all watermark manually. export as pdf shows the same result. Steps to Reproduce: 1. open pdf file in pdf reader 2. open pdf file in draw 3. check all pages from second page onward. see watermark Actual Results: watermark is shown front and opaque which overlaps the text. only option is to delete the watermark one by one Expected Results: watermark should be rendered properly just like pdf file has Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.4.2 / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Flatpak Calc: threaded
https://bugs.documentfoundation.org/attachment.cgi?id=173736 input file for test https://bugs.documentfoundation.org/attachment.cgi?id=173738 output of draw
Created attachment 173739 [details] screenshot of draw
confirm in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 0d4cbdbc9cd4ab06056cec66cffd292b41615b6e CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded
confirmed in Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Flatpak Calc: threaded
Dear johnks, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
confirmed in Version: 25.2.3.2 (X86_64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 17763); UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: CL threaded