Bug 84528 - FILESAVE: Corruption when saving in ODP Format
Summary: FILESAVE: Corruption when saving in ODP Format
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Keywords: possibleRegression
Depends on:
Reported: 2014-09-30 20:14 UTC by Kim Mongan
Modified: 2015-12-15 10:57 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Kim Mongan 2014-09-30 20:14:56 UTC
Problem description: When saving a presentation in ODP Format the presentation is corrupted.  It appears that the first bitmap background for a presentation is transferred to all following bitmap backgrounds.  This does NOT happen when saving in Microsoft PPT Format.  This has been happening with all releases of 4.3 that I tested.  You definitely need to do better testing of this before releasing a new version because this is a bad case scenario when you work is being corrupted, especially when saving in the native format of LibreOffice.
Operating System: Windows 7
Version: release
Last worked in: release
Comment 1 Owen Genat (retired) 2014-10-05 06:37:07 UTC
Please provide an example ODP created under a prior version of LO that saves as expected and repeatedly saves in the indicated corrupt manner under v4.3. Older versions of LO available here:


This will allow others to confirm the problem. Status set to NEEDINFO. Please set back to UNCONFIRMED once the requested information is provided. Thanks.
Comment 2 QA Administrators 2015-05-06 14:15:08 UTC
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!

Warm Regards,
QA Team
Comment 3 QA Administrators 2015-06-08 14:26:49 UTC
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

Warm Regards,
QA Team
Comment 4 Robinson Tryon (qubit) 2015-12-15 10:57:51 UTC
Migrating Whiteboard tags to Keywords: (possibleRegression)