Hi Everyone, I am using Impress 6.4.7.2 on Ubuntu 20.04, x86_64, fully patched. When I rename a slide by right clicking slide and then selecting "Rename Slide", the slide is renamed. If I right click the slide again and then select "Rename Slide", I see the new name. If I export the slide deck as PDF, I also see the renamed slides. However, if I save and close the slide deck and the reopen the slide, the changes are lost. If I right click the slide after reopening and then select "Rename Slide", then I see the names revert back to "Slide 1", "Slide 2", etc. It looks like this issue has been around a while: https://forum.openoffice.org/en/forum/viewtopic.php?t=28732. However, I did not see it reported to the dev team. ----- This may be useful to the dev team... If I open a second deck, rename a slide, and copy/paste the slide from second deck into the first deck, then the rename is persistent. I can save, close and open the first deck and the new name sticks. Very weird... ----- $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal $ apt-cache show libreoffice-impress Package: libreoffice-impress Architecture: amd64 Version: 1:7.2.6-0ubuntu0.21.10.1~bpo20.04.1 Priority: optional Section: editors Source: libreoffice Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian LibreOffice Maintainers <debian-openoffice@lists.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 10264 Provides: libreoffice-ogltrans Depends: libreoffice-common (>= 1:7.0.0~alpha~), libreoffice-core (= 1:7.2.6-0ubuntu0.21.10.1~bpo20.04.1), libreoffice-draw (= 1:7.2.6-0ubuntu0.21.10.1~bpo20.04.1), ucf (>= 0.8), libc6 (>= 2.29), libepoxy0 (>= 1.0), libetonyek-0.1-1, libgcc-s1 (>= 3.0), libodfgen-0.1-1, librevenge-0.0-0, libstdc++6 (>= 5), libuno-cppu3 (>= 4.4.0~alpha), libuno-cppuhelpergcc3-3 (>= 5.3.0~alpha), libuno-sal3 (>= 5.3.0~alpha), libuno-salhelpergcc3-3 (>= 1.4.0), uno-libs-private Suggests: bluez Conflicts: libreoffice-ogltrans (<< 1:6.1.4-2~) Breaks: libreoffice-common (<< 1:6.4.2~rc1~) Replaces: libreoffice-common (<< 1:6.4.2~rc1~), libreoffice-ogltrans (<< 1:6.1.4-2~) Filename: pool/main/libr/libreoffice/libreoffice-impress_7.2.6-0ubuntu0.21.10.1~bpo20.04.1_amd64.deb Size: 1242412 MD5sum: cb439003197f7a408fe74e24b47dae93 SHA1: 876b85ce86f49692e4b061205df6506f7c403e93 ...
Created attachment 179905 [details] Sample ODP with renamed slide (OK) Can't reproduce, see attached file. Fine both with LO 6.4.7.2 included in Ubuntu 20.04 (which is a fairly old version), and with LO Version: 7.4.0.0.alpha0+ (75fe4051320ef9b1f4323fa958e8df3db2066882).
Dear Noloader, 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 Noloader, 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