I found that problem during my research for "Bug 49646 - FILEOPEN .pptx in notes view: note and sheet contents shown outside sheet area at top left", problm is reproducible with Attachment 61765 [details] Steps how to reproduce with parallel installation of Master "LOdev 4.0.0.0.alpha0+ - ENGLISH UI / German Locale [Build ID: a2b3ee)]" {tinderbox: @6, pull time 2012-11-13 06:07:28} on German WIN7 Home Premium (64bit) with separate /4 User Profile for Master Branch: 1. Open new Presentation from LibO Start center 2. Rename first slide to "My Name" after right click on slide in slides pane 3. Close / reopen Bug: Slide now shows default name "Slide 1" instead of "My Name" Already reproducible with LibO 3.3.3, seems that never workked correctly. Because names are shown correctly when I open att. of Bug 49646 I am sure that it's a FILESAVE problem. Data loss, so "major"
not reproducible with 3.6.3.2
Reproducible with LibO 3.5.4.2 on Ubuntu 12 64Bit @A: Without information concerning test conditions, your OS and so on your comment is not very useful.
Confirmed with 3.7.0.0-alpha on Ubuntu 12.04 x86_64
(In reply to comment #1) > not reproducible with 3.6.3.2 Windows 7 - 64Bit
It seems getting worst..after doing steps on comment 0 all slides name reset to Slide 1, Slide 2, Slide 3, and so on. Tested on LO 4.0.4.1 (Win7 32bit)
** 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 (4.4.1 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
Still reproducible with LibreOffice 4.4.3.0.0+ built at home under Ubuntu 14.10 x86-64 Workaround: use OpenDocument format (.odp) Best regards. JBF
** 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.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Still reproducible in LO 5.1.4.0.0+ and master, both build at home under Ubuntu 16.04 x86-64. Best regards. JBF
** 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.2.7 or 5.3.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-20170522
Still reproducible with LO 5.4.1.0.0+ built at home under Ubuntu 16.04 x86-64. Best regards. JBF
still repro in Version: 6.2.0.0.alpha0+ Build ID: 1aa37aa6bee19099b57555a6d839992b054aa405 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-09-23_10:17:54 Locale: ru-RU (ru_RU); Calc: threaded
Still repro Version: 6.4.0.0.alpha0+ (x64) Build ID: e1b51d4588b4b39592bb94dd5bb90de5e04d061e CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-23_09:16:11 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
Still getting reproduced in: Version: 6.4.4.2 (x64) Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Recently this got better after: https://git.libreoffice.org/core/+/b6b02e0b4c9d739836e1f61a886ea45b01e6696e author Attila Bakos (NISZ) <bakos.attilakaroly@nisz.hu> Tue Apr 20 13:02:44 2021 +0200 committer László Németh <nemeth@numbertext.org> Thu Apr 29 10:48:27 2021 +0200 tdf#111903 tdf#137152 PPTX export: fix placeholders Now changed slide titles survive the roundtrip. Also previously the Outline view got completely empty after roundtrip, now that also survives. Thanks Attila for solving this as well :) Note: PPTX does not really store the slide title, that's a LO-thing. Actually the Title boxes content is shown here and in the Navigator/Outline view as well. When modifying any of these, these are not all synchronized in the editor, but after PPTX roundtrip they are.
When opening 47-slide MSO Attachment 61765 [details], in LO 7.2+ I see Slide 1, Objectives,.., Slide 6, Estimation,.., Slide 9, Slide 10,.. Slide 1 name is not read from OO. Slide 6 is a consequence of being the same as of slide 5, change in bug 103347 (solved by renaming same name to Slide X and not to Existing Slide Name (1)). If saved as PPTX and reopen in LO, Slide 1 name is proper, Slide X remain, but renamed slide is not remembered. In MSO all names are proper (renamed slide still shown as original). So I don't see this fixed. If it is, please explain. As for Importance, I set Low-Normal, because as explained this is LO-only feature. Note that MSO asks to repair PPTX coming from LO-saved Attachment 61765 [details] (another issue, seems not regression).
Ah, so many different issues still... this file if inspected more closely, could also be a treasure trove of "improvement opportunities". (In reply to Timur from comment #16) > When opening 47-slide MSO Attachment 61765 [details], in LO 7.2+ I see Slide > 1, Objectives,.., Slide 6, Estimation,.., Slide 9, Slide 10,.. > Slide 1 name is not read from OO. Indeed! But that's a separate pre-existing fileopen issue. I'll file a new bug for that. Long (64 char+) slide names are also turned into "Slide N" format, instead of being truncated a bit + numbered; like on the last two slides. I'll file a new bug about this as well. Finally there are slides without a Title box, I think for those the default Slide N is viable. For example in PP the Custom Slide Show dialog refers to the slides by their Title box contents and slides without any Title box appear as Slide N even in PP, such as slide 13, 18, 36, 42 in this example file. > Slide 6 is a consequence of being the same > as of slide 5, change in bug 103347 (solved by renaming same name to Slide X > and not to Existing Slide Name (1)). > I think we should change that. > If saved as PPTX and reopen in LO, Slide 1 name is proper, Slide X remain, > but renamed slide is not remembered. In MSO all names are proper (renamed > slide still shown as original). How did you rename it? Using the Rename Slide box does not retain the new content, but changing the actual slide title in the editor works after reload and fills the name in the Rename Slide box and Navigator as well. Since slide name is generated from the Title placeholders in case of PPTX, I think this is as far as we can go. Unless we want to start to explore options to disable the Rename Slide functionality upon opening a PPTX file. > So I don't see this fixed. > If it is, please explain. > This bug was about the view of the LO-saved PPTX in LO, which improved dramatically compared to the former complete loss of generated contents in the Navigator and also in the Overview view. But there is still some room for improvement, thanks for noticing :). > As for Importance, I set Low-Normal, because as explained this is LO-only > feature. > > Note that MSO asks to repair PPTX coming from LO-saved Attachment 61765 [details] > [details] (another issue, seems not regression). I can't reproduce this issue anymore. The example file when saved with todays nightly opens fine in my PP 2019: Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 3b57ebb445df8a2bc3d916ea79f8af45e20e4e62 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL However it was indeed repaired if I saved it with 7.1.0.
(In reply to NISZ LibreOffice Team from comment #17) Thanks for all. > How did you rename it? > Using the Rename Slide box does not retain the new content, but changing the > actual slide title in the editor works after reload and fills the name in > the Rename Slide box and Navigator as well. I used right-click rename, as in Comment 0. Maybe with that this bug should be NotOutBug or WontFix.
I'm closing as WontFix. If someone can explain better, feel free to mark.