I tried to frame an image using shapes. To my knowledge there are two ways to do that. First, draw a basic shape (hexagon, circle..) and fill the area with a bitmap image form file. The result is the image goes outside the shape line and is not cut along the shape lines. Actually, the image fills the rectangle enveloping the shape. Second method, insert image draw basic shape over it, select all, and than intersect, gives exactly the same result as above. First method was tested with Draw and Writer, and second only with Draw. OS: OpenSuse Tumbleweed x64 LibreOffice 6.2.1.2 BuildID:20 (build 2). Framing image by both methods worked in Libre 6.0.1.1 release. Also mentioned that drop list for bitmap styles contents only 3 entries in 6.2.1.2, whereas in 6.0.1.1 there used to be more options.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 150809 [details] The file contains two shapes (stars) filled with pattern and bitmap As you can see the filling is not cut along the edge line of the shape.
[Automated Action] NeedInfo-To-Unconfirmed
Hello, Please attached a screenshot showing how it looks for you. it's fine in Version: 6.3.0.0.alpha0+ Build ID: 64faea31f7d05e46fe5c91f87381ec7abae90174 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 151283 [details] Screen print of shapes filling in 6.2.3.2 Build ID: 20(Build:2).
(In reply to densp from comment #5) > Created attachment 151283 [details] > Screen print of shapes filling in 6.2.3.2 Build ID: 20(Build:2). Weird. It is fine in 6.2.3 for me Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded Also fine on Linux. Could you try with an appimage of 6.3: https://libreoffice.soluzioniopen.com/ Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: b9a776837462eeb6d50d0decc42604c0c3008eb1 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 11 August 2019
(In reply to Buovjaga from comment #7) > Could you try with an appimage of 6.3: https://libreoffice.soluzioniopen.com/ Setting to NEEDINFO
Dear densp, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear densp, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp