I am experiencing a number of problems when I insert animated gifs into a slide in a presentation.
First, overall performance starts to slow down quickly, and at times adding another animated gif, or sometimes just changing to a new slide (by clicking on one in the slide pane) will freeze my entire system for several seconds, sometimes 10s of seconds, including the mouse.
Also, the image is usually inserted correctly (see screenshot 1), but often (not always; it is intermittent) if I move to another slide, then back to the slide with the inserted animated gif, it is no longer displayed and instead I see an empty frame with a small icon and three periods at the top (see screenshot 2). When this happens, the image is also not displayed during slideshows, which means that showing animated gifs is completely broken for me, because I cannot rely on them being shown correctly.
These two issues seem to be related. If I have an animated gif showing correctly, and I then add another to another slide, and there is no long freeze to add the image, then the first image will still be displayed OK. But if I add the second image (or change slides) and experience the several-second freeze, I know that when I go back to the first slide, it sill not be displayed correctly. In the second screenshot, I had to add several new gifs to get this behavior to happen. You can see in screenshot 1 that I have images on 4 slides. In screenshot 2, I added an image to slide 5, no problem, then 6, no problem, then for slide 7, my system hung for about 8 seconds before adding that image. Then, all of the 6 previous images showed a blank frame like in screenshot 2.
One thing I notice is that in Powerpoint, animated gifs are shown as static images in the editor, and are only animated during the slide show. This may help with the performance issues I am experiencing.
In addition to the screenshots, I have attached several animated gifs for testing, along with the presentation file in the screenshots.
Nothing is attached. Marking as NEEDINFO. Also for future reports please give explicit enumerated reproducible steps to begin with. It's much easier for QA to handle short enumerated steps than digging through paragraphs of writing. Just keep in mind that we have to deal with thousands of bug reports and we're all volunteers ;) The easier you make it on us the more we are likely to get through the bug triage process happy.
Marking as NEEDINFO - once you provide reproducible steps and the attachments that you stated you attached set to UNCONFIRMED. Thanks!
Dear Bug Submitter,
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 INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
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!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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
-- The LibreOffice QA Team
This INVALID Message was generated on: 2015-05-06