Bug 105715 - going back impossible in presentation after a certain slide with grouped custom animations
Summary: going back impossible in presentation after a certain slide with grouped cust...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Slide-Show Object-Animations
  Show dependency treegraph
 
Reported: 2017-02-02 21:26 UTC by documentfoundation
Modified: 2023-11-06 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
presentation in which going back is not possible on slide 14 (1.92 MB, application/vnd.oasis.opendocument.presentation)
2017-02-02 21:26 UTC, documentfoundation
Details
presentation where back not possible on slide "14" - 3 slides (235.59 KB, application/vnd.oasis.opendocument.presentation)
2017-02-03 14:54 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description documentfoundation 2017-02-02 21:26:17 UTC
Created attachment 130867 [details]
presentation in which going back is not possible on slide 14

I created a presentation where it is not possible to "go back" on one slide - i do not see what could cause that and I for sure have not caused that intentionally. 

Copying the slide in a new presentation does not reproduce the bug so I do not have a MWE, sorry

reproduce: go to slide 14, try to go to previous slide.

also affected: lo-5.3 I did not try with other releases.
Comment 1 Timur 2017-02-03 14:54:54 UTC
Created attachment 130880 [details]
presentation where back not possible on slide "14" - 3 slides

Here is that presentation reduced to 3 slides. 
Going back is not possible on on slide "14" because of slide "13". 
When custom animations on "13" are deleted, it is possible. 
Those animations seem pointless, since images are grouped, and uncorrect. 

So, this might be a bug, because Impress should not be confused, and doesn't have to be, or is lowest, because example is not correctly created.
Comment 2 Thomas Woltjer 2017-02-03 19:46:31 UTC
Reproduced in 

Version: 5.1.6.2.0+
Build ID: 5.1.6.2 Arch Linux build-5
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.utf8); Calc: group

and in

Version: 5.3.0.3
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new; 
Locale: en-US (en_US.utf8); Calc: group
Comment 3 QA Administrators 2018-05-18 02:32:49 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2019-03-31 11:59:46 UTC
still repro in

Version: 6.3.0.0.alpha0+
Build ID: 1e2868296730d3548574f61a3c6e323aa5c0598a
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-03-28_20:38:05
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 5 Buovjaga 2021-11-05 14:53:21 UTC
Still repro

Arch Linux 64-bit
Version: 7.3.0.0.alpha1+ / LibreOffice Community
Build ID: ae0767b0fbe5d5b56ebe406bf1ee7aca4aaa909f
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 5 November 2021
Comment 6 QA Administrators 2023-11-06 03:13:18 UTC
Dear documentfoundation,

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