Since libreoffice 4.2.6 stable and with all newer versions: Some Draw documents always corrupt picture links for liked images. Under 'EDIT/LINKS..' all picture paths appear as: [pathName]/[pictureName.extension]?requestedName=[pictureName] If I delete "?requestedName=[pictureName]" manually from every entry under 'EDIT/LINKS..', all images are displayed correctly. Saving the document and reopening causes the same error again.
(In reply to comment #0) > Since libreoffice 4.2.6 stable and with all newer versions: > Some Draw documents always corrupt picture links for liked images. Under > 'EDIT/LINKS..' all picture paths appear as: > [pathName]/[pictureName.extension]?requestedName=[pictureName] > > If I delete "?requestedName=[pictureName]" manually from every entry under > 'EDIT/LINKS..', all images are displayed correctly. Saving the document and > reopening causes the same error again. Hi troudel, Could you please attach an example file that demonstrates this behavior? After the upload, please change the status from NEEDINFO -> UNCONFIRMED. Thanks!
I have the same exact problem. Linked images disappear after save. This affects Draw and Presentation but is OK in Writer. I found the way to reproduce it: 1. Download the attached files D1.odg, D1.odt, D1.odp and IMG_0570s.jpg into the same directory. 2. Open D1.odg, the image should appear. 3. Move the image a little bit, press save, move it again, press save. 4. Close the file. 5. Open it again and the image has vanished. It can be fixed manually by Edit/Links... as described earlier. Notice in 3 that you need to save the file twice for the link to be corrupted. After one save it seems OK. The presentation D1.odp is affected in the same way but the Writer file D1.odt works fine. Maybe someone can make sense out of this.
Created attachment 106735 [details] Draw file
Created attachment 106736 [details] Presentation file
Created attachment 106737 [details] Writer file
Created attachment 106738 [details] Image file...
Hi all.. Seems a duplicate to Bug 80849. Should be fixed in 4.2.7 & 4.3.1
TESTING with LO 4.3.2.2 + Ubuntu 14.04 (In reply to comment #2) > I have the same exact problem. Linked images disappear after save. This > affects Draw and Presentation but is OK in Writer. I found the way to > reproduce it: > > 1. Download the attached files D1.odg, D1.odt, D1.odp and IMG_0570s.jpg into > the same directory. > 2. Open D1.odg, the image should appear. Confirmed > 3. Move the image a little bit, press save, > 3b. Move it again, press save. > 4. Close the file. > 5. Open it again and the image has vanished. It can be fixed manually by > Edit/Links... as described earlier. NO REPRO -- Image remains visible > The presentation D1.odp is affected in the same way NO REPRO -- Image remains visible > but the Writer file > D1.odt works fine. This part I can confirm: The image does remain visible, as OP describes. Status: Let's get confirmation on Windows before we mark the bug as RESOLVED.
In Draw or Impress Edit - Links, I don't have the path like in the report description. Yet, I have to click Update to make the image visible. The status in the Edit - Links dialog is Manual. I have to click Update even, if I save & reopen. In Writer, the image is displayed on opening. For some reason I see a quick flash of Read error in the image frame before it appears, though. I could also reproduce from scratch. Setting to NEW and lowering severity per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: b144f0ac8695dd62a2053b4e88212d0b109c9a41 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-25_00:14:54
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Dear troudelalmanach, 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
Creating both my own test as well as using the supplied sample files and following the steps to reproduce, could not reproduce in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7a0e0a84a02f505200331c19b28d45e898cd5a12 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Was working great right up to the point where MalWareBytes flagged today's build of LibreOffice 7.2 Dev as ransomware and quarantined the entire program.
Thanks, let's go ahead and close