Bug 117493 - adding animation to a raster object makes LO crash
Summary: adding animation to a raster object makes LO crash
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-08 08:09 UTC by Andy
Modified: 2018-05-28 11:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Use this file as instructed to reporduce the bug (302.94 KB, application/vnd.oasis.opendocument.presentation)
2018-05-08 08:10 UTC, Andy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2018-05-08 08:09:50 UTC
Description:
Adding animations to bitmap in a slide causes the whole app to crash

Steps to Reproduce:
1. open the attached file "Animation on raster crashes LO.odp". You'll find a nice animated gif of the earth on the slide
2.Now select the object, go to the sidebar, personalised animation tab, and click on the "+" button to add an animation to the object
3. Lo will crash and close.

Actual Results:  
This happens with a number of bitmaps, not ANY image. The object in the attach is an example leading to systematic crash.
Note that this does not happen when adding animations to other kind of objects, and if you place in the same slide another object, EG a text, and set an animation for it first, then you can set one for the earth as well and the crash is avoided

Expected Results:
You should be able to set animations to bitmap objects anytime without crashing LO


Reproducible: Always


User Profile Reset: No



Additional Info:
I tried to disable OpenGL, and in this way I could add the animation. However, when I clicked the "X" button to delete the animation associated to the earth object, LO crashed. It seems this procedure is highly unstable.
I could not say for certain if this was a problem in previous version, but I suspect this did not always happen: attaching animations to bitmap objects is a common action I have always performed very often, but I do not remember having this problem in the past, say a year or two ago


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Andy 2018-05-08 08:10:29 UTC
Created attachment 141965 [details]
Use this file as instructed to reporduce the bug
Comment 2 Xisco Faulí 2018-05-08 08:35:10 UTC
I can't reproduce it in

Versión: 6.0.3.2
Id. de compilación: 8f48d515416608e3a835360314dac7e47fd0b821
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; 
Configuración regional: es-ES (es_ES); Calc: group

nor in

Version: 6.0.4.2
Build ID: 1:6.0.4~rc2-0ubuntu0.16.04.1
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 3 Andy 2018-05-08 08:55:09 UTC
Ok, in the next few days I will test it with a fresh installation and report about it. Thanks
Comment 4 Andy 2018-05-14 09:25:17 UTC
Yes you're right, I tried it on a brand new install of 6.0.4.2 made with reisisoft separate install gui and the problem is not there.
However the idea of wiping out the settings of my user profile and recreating them all from scratch is fearsome... a quite dauting work. Any suggestions or workaround to avoid this??
Thanks indeed
Comment 5 Andy 2018-05-14 10:15:10 UTC
News: problem is not occurring with 6.0.4.2 in my old install as well (I was testing iit on 6.0.3). This solves it I think
Comment 6 Xisco Faulí 2018-05-28 11:02:58 UTC
(In reply to Andy from comment #5)
> News: problem is not occurring with 6.0.4.2 in my old install as well (I was
> testing iit on 6.0.3). This solves it I think

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.