Problem description: When copying over two media files from two separate .PPTX files into one odp presentation, only one of the videos is preserved when saving and reopening the file. Some technical details I can provide: Powerpoint calls the media files media1.wmv and counts up on that number. When a presentation only contains one video, it is called media1.wmv. When having two videos in two different presentations, each is called media1.wmv. I assume that this name collision is causing the loss of one video file Steps to reproduce: 1. Download the two presentations https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_1.pptx and https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_2.pptx 2. Open the two presentations in libreoffice 3. Create a new odp presentation. 4. Copy over the two video files into this new presentation using copy and paste (At this point, everything is still fine) https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_1.png 5. Save the presentation as odp 6. Close the presentation 7. Reopen the presentation, you can now clearly see that the first video was replaced by the second https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_2.png Current behavior: When saving and reopening the file, one of the two videos is permanently lost. https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_2.png Expected behavior: Both videos should be preserved. When there are two videos with the same name, one should be renamed unless there is reason to believe they are identical (e.g., matching md5 sum). https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_1.png Thanks again for all your efforts.
Created attachment 118340 [details] First .PPTX with video
Created attachment 118341 [details] Second pptx with video
Created attachment 118343 [details] Screenshot of healthy file before saving and reopening
Created attachment 118344 [details] Screenshot of corrupted file after reopening
Created attachment 118345 [details] Resulting corrupted odp file
True! Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit) Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: fi-FI (fi_FI)
** 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.5 or 5.2.1 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-20160920
Yes, the bug is still present. This is the result obtained on LO 5.1.5.2 using Windows 10: https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug19_2016.odp One of the videos is still lost.
** 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 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
Dear ravingdesi, 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
Still reproducible in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: d46f16bb3b1efbf8dc8835221e8e861de4364716 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Still in 7.4+. There's also a regression with opening source PPTX, edit and presentation. Not with 4.2.0. Seen with LO 4.3 up to 7.4+ in Windows GDI and Skia, not Linux.