| Summary: | adding animation to a raster object makes LO crash | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Andy <silvandy> |
| Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | xiscofauli |
| Priority: | medium | ||
| Version: | 6.0.3.2 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | Use this file as instructed to reporduce the bug | ||
|
Description
Andy
2018-05-08 08:09:50 UTC
Created attachment 141965 [details]
Use this file as instructed to reporduce the bug
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 Ok, in the next few days I will test it with a fresh installation and report about it. Thanks 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 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 (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. |