Created attachment 146150 [details] ODS-File I use button in a calc-sheet (form control) with a linked PNG-file. In LO 6.0.1.1 is all correct. If I start the sheet with 6.1.1.2, then the button is without the PNG-file. The properties for the picture at the button are lost. Sorry for my bad english.
Created attachment 146151 [details] Corresponding PNG-file
Created attachment 146171 [details] test file created with LO 5.4.7.2 your attached file has an *absolute* link to the png file: <form:button form:name="PushButton" form:control-implementation="ooo:com.sun.star.form.component.CommandButton" xml:id="control1" form:id="control1" form:label="Ende OHNE Speichern" xlink:href="" form:image-data="file:///K:/Daten/Tools%20&%20Technik/OpenDocumentFormat/Musterdateien/Kasse/VR_Icon_09.png" form:delay-for-repeat="PT0.050000000S" form:image-position="top" form:image-align="center"> but i think this is a bug: - downloaded file and png into same folder - opened file with LO 5.4.7.2/LO 6.0.7 and added the file URL. - LO will save a *relative* URL: <form:button form:name="PushButton" form:control- implementation="ooo:com.sun.star.form.component.CommandButton" xml:id="control1" form:id="control1" form:label="Ende OHNE Speichern" xlink:href="" form:image-data="../VR_Icon_09.png" form:delay-for- repeat="PT0.050000000S" form:image-position="top" form:image-align="center"> - save and reload: png is visible - open file with LO 6.1.3.1: png is not visible caused by new graphic handling in LO 6.1?
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=9fb7aaf570c03c8a26d763f1205fb8c890e8211a author Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> 2018-04-13 16:58:49 +0900 committer Tomaž Vajngerl <quikee@gmail.com> 2018-04-16 02:52:02 +0200 commit 9fb7aaf570c03c8a26d763f1205fb8c890e8211a (patch) tree 8f4466b24d9fcae2da5043479a57fabc662a2c43 parent ba69036c8e889237da4bb312d7c5c94066abbfd3 (diff) Make linked graphic register into LinkedManager again Bisected with: bibisect-linux64-6.1 Adding Cc: to Tomaž Vajngerl
Dear BGWitt, 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
Repro 7.3+ with attachment 146171 [details].
Dear BGWitt, 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