Bug 90323 - FILESAVE: Impress document Save As does not completely clear modified status
Summary: FILESAVE: Impress document Save As does not completely clear modified status
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.4.1.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-29 14:42 UTC by Pieter van Oostrum
Modified: 2016-05-09 20:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pieter van Oostrum 2015-03-29 14:42:15 UTC
An impress document, saved with Save As, still has some kind of modified status, and will not close without complaining.

To reproduce:

- Open an Impress document
- Make some changes
- Save as a different file type, for example powerpoint.
Now the icon in the status bar shows "not modified". Also on Mac OS X the window close button shows the "not modified" status
- Close the document: Now a message box comes up with "Save changes to document "xxx" before closing?" which is completely unnecessary, as the saved document is identical to the document in memory.
- Click Cancel.
Now the status bar shows the "modified" icon. Also the Mac OS X window close button shows the modified form.
Comment 1 Alex Thurgood 2015-03-30 17:17:55 UTC
Sorry, where is the bug ?

If I save as PPTX, the document on screen is a PPTX document, and as no changes have taken place since I saved it as such, I can close the window by clicking on the top left hand button of the window frame, and not get asked whether I want to save - this is the correct behaviour.

Please explain more clearly, if you feel I have missed something.

Tested on :
Version: 4.5.0.0.alpha0+
Build ID: 09f83e1f409853a6c6e4300287c4e50bad5b9d0b
Locale: fr_


OSX 10.10.2

Setting to NEEDINFO pending explanations.
Comment 2 Pieter van Oostrum 2015-03-30 17:53:52 UTC
Well, I do get asked to save the document.

Version: 4.5.0.0.alpha0+
Build ID: 4f9e20c46b616c7c51bae74bfefd5247f922b2a6

Mac OS X 10.10.2

Please note that you must have made some changes to the document, otherwise there will be no problem. And even stranger, if you save the document first (i.e. to the original document that you loaded, and the do a 'Save as PPTX' it still asks you if you want to save.

If you still don't see this behaviour, it might be related to Preferences.
Comment 3 QA Administrators 2015-10-14 19:50:28 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: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

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

This NEEDINFO message was generated on: 2015-10-14
Comment 4 QA Administrators 2016-05-09 20:07:15 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

Warm Regards,
QA Team

This INVALID Message was generated on: 2016-05-09