Created attachment 136483 [details] Sample slide to show the problem Steps to reproduce: 1. In Impress open AnimationTimingBug.odp 2. F5 3. Change Slide transition to None OR remove green textbox from master slide 4. F5 Note the middle animations are played simultaneously instead of sequentially as their timings are set to "After Previous"
On pc Debian x86-64 with master sources updated today, I noticed this on console: (soffice:4920): Gtk-WARNING **: Allocating size to OOoFixed 0x55e7a91d77e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? warn:legacy.osl:4920:4920:slideshow/source/engine/activities/activitiesfactory.cxx:418: createFromToByActivity(): Could not extract by value warn:slideshow:4920:4920:slideshow/source/engine/animationnodes/animationbasenode.cxx:210: (com.sun.star.uno.RuntimeException) { { Message = "slideshow::internal::AnimationActivitySharedPtr slideshow::internal::{anonymous}::createFromToByActivity(const com::sun::star::uno::Any&, const com::sun::star::uno::Any&, const com::sun::star::uno::Any&, const slideshow::internal::ActivityParameters&, const std::shared_ptr<_Up>&, const slideshow::internal::Interpolator<typename AnimationType::ValueType>&, bool, const ShapeSharedPtr&, const basegfx::B2DVector&) [with BaseType = slideshow::internal::ContinuousActivityBase; AnimationType = slideshow::internal::PairAnimation; slideshow::internal::AnimationActivitySharedPtr = std::shared_ptr<slideshow::internal::AnimationActivity>; typename AnimationType::ValueType = basegfx::B2DTuple; slideshow::internal::ShapeSharedPtr = std::shared_ptr<slideshow::internal::Shape>],\X000acreateFromToByActivity(): Could not extract by value", Context = (com.sun.star.uno.XInterface) @0 } }
I can't reproduce it with LO 5.4.2.2 / Windows 7, either. Which version did you use? Can you upload the version where the animations fail to play correctly?
Aron Budea, I have no problem reproducing this with both Windows and Linux. Just confirmed now on Version: 6.0.0.0.alpha0+ (x64) Build ID: 2e8a95d1f87a3dbdcc8846fa44d1899abc8edd9c You have to look for no more than 1 shape should disappearing at once. They should fade in and out ONE AT A TIME, from left to right. Try changing the Slide transition to None OR removing the green textbox from master slide to see how the effects should look. When it's working only one blinks in and out at a time. When it's not working several of the shapes blink at once. The other option is this is a performance issue and you need to try this on a slower PC. I have now verified this issue on 2 laptops and 1 desktop.
(In reply to Luke from comment #3) > Aron Budea, > I have no problem reproducing this with both Windows and Linux. Just > confirmed now on Version: 6.0.0.0.alpha0+ (x64) > Build ID: 2e8a95d1f87a3dbdcc8846fa44d1899abc8edd9c Hi Luke Should it be closed then?
(In reply to Xisco Faulí from comment #4) > Should it be closed then? He wrote he could consistently reproduce it, so likely not. I can't repro the issue, though (tried again with the latest status of bibisect-linux-64-6.0), so other attempts are welcome. Let's return status to UNCONFIRMED in the meantime.
I am unable to repro. My machine is probably too fast, though. Arch Linux 64-bit Version: 6.0.0.0.alpha1+ Build ID: 17cfe6e25d479428de308c22fcd218dcf8827840 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 15th 2017 Version: 6.0.0.0.alpha1+ (x64) Build ID: 4058d85963e371be657f531d8f30e31381a9ccab CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-05_22:51:05 Locale: fi-FI (fi_FI); Calc: group
Also no repro. Even if this is true, is it realistic someone will fix it for slow comps? Unlikely. Since already 3 of us couldn't, I set to Needinfo until you find reasons (and update title) or close it.
This **IS** a performance issue as I can repro it on three i3 and slower PCs, while I cannot reproduce it on my i7 desktop. However, if you use the original file that's not stripped down: https://skydrive.live.com/view.aspx?resid=9FBE63963526EB25!411&app=PowerPoint&wdo=2&authkey=!AN5Q_kKPvn2eWUQ Even that is animated incorrectly on my i7. I suggest you 3 with beefy machines try out that file instead.
(In reply to Luke from comment #8) > This **IS** a performance issue as I can repro it on three i3 and slower > PCs, while I cannot reproduce it on my i7 desktop. However, if you use the > original file that's not stripped down: > > https://skydrive.live.com/view.aspx?resid=9FBE63963526EB25! > 411&app=PowerPoint&wdo=2&authkey=!AN5Q_kKPvn2eWUQ > > Even that is animated incorrectly on my i7. I suggest you 3 with beefy > machines try out that file instead. I seem to remember there being a report for that presentation already. It does have glitchy animations, but not like in your original description/file.
Sorry I linked to the wrong demo above. Here is the correct link. You can play this demo live on the web or play in in Powerpoint to see how the animations should look. https://onedrive.live.com/view.aspx?cid=9fbe63963526eb25&page=view&resid=9FBE63963526EB25!718&parId=9FBE63963526EB25!103&authkey=!AN5Q_kKPvn2eWUQ&app=PowerPoint There are other issues with how we display this presentation, but this bug report is how we handle our timing. When the Slide transition are enabled on slow machines something delays the animations from starting. We they do start rather than play in order, they all play at once. Once a developer takes a look at this, they may ask that we break this into 2 issues, the poor performance and the bug causing the timings to not be respected.
(In reply to Luke from comment #10) > Sorry I linked to the wrong demo above. Here is the correct link. You can > play this demo live on the web or play in in Powerpoint to see how the > animations should look. > > https://onedrive.live.com/view. > aspx?cid=9fbe63963526eb25&page=view&resid=9FBE63963526EB25! > 718&parId=9FBE63963526EB25!103&authkey=!AN5Q_kKPvn2eWUQ&app=PowerPoint Ok, with this I see the second speaker and the screen next to it fading at the same time in slide 2. Arch Linux 64-bit Version: 6.1.0.0.alpha1+ Build ID: 03a4b6eb58b29c0ab4bb85f756923c46618d02ff CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 2nd 2018
Created attachment 141900 [details] Heavier example
After the animation plays, if you press: 1) left arrow 2) space to replay the animation, the 2nd and all subsequent times it will render properly even on a slow PC.
Dear Luke, 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 on Version: 6.4.0.0.alpha1+ (x64) Build ID: 36022becbe25c412460411ab50ecaf7740933dca CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: default; VCL: win;
Dear Luke, 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
still reproducible on 7.3