Bug 81754 - Not saving latest editions in ODF
Summary: Not saving latest editions in ODF
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:5.4.0
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-25 17:19 UTC by Olivier Hallot
Modified: 2019-05-15 09:35 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
presentation indicating the loss of the latest edition in open obejcts for editing (95.70 KB, application/vnd.oasis.opendocument.presentation)
2014-07-25 17:19 UTC, Olivier Hallot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Hallot 2014-07-25 17:19:14 UTC
Created attachment 103460 [details]
presentation indicating the loss of the latest edition in open obejcts for editing

LibreOffice Impress is not saving latest editions.

When editing a text box in Impress and I click on Save file, the editions of the text box are lost.

The attached sample shows it. This file is a presentation that were PPT/PPTX in a previous life.

To see the bug:
1) Open the file
2) edit the text in the first slide
3) click on Save in the toolbar
4) close the file
5) reopen the file

Effect: your edition in the text box are lost.

To circumvent this bug:
Option 1
Click out of the text box to commit the latest edition, only then save the file.

Option 2
close the file. A warning box will inform the edition were not saved. Click to save it.

Option 3
Select all content of the text box
Delete the text box
Create a new text box
Copy back the contents into the new text box.

Expected behaviour:

File saved with the latest edition of the text box.
Comment 1 Ken Biondi 2014-07-26 20:15:10 UTC
Hello Olivier,

I could not reproduce your bug, so I changed the status to resolved-worksforme.

If this is still a bug for you change the status back to unconfirmed and provide more information if possible.  You might consider upgrading LO to a later version since it worked for me on 4.2.5.2.

I tested using:

x86-64
Windows 8
LO Version: 4.2.5.2
Build ID: 61cb170a04bb1f12e77c884eab9192be736ec5f5
Comment 2 Jan Holesovsky 2017-01-03 16:23:39 UTC
This has to be a pptx file; not reproducible with .odp for me, but I can reproduce with a pptx.

Another interesting thing: In this scenario - after saving, the "save status" shows that the file has been saved.  But when closing the document, it becomes unsaved again, and the user is asked whether to save the changes.
Comment 3 Aron Budea 2017-01-04 17:43:12 UTC Comment hidden (bibisection)
Comment 4 Aron Budea 2017-01-04 17:44:00 UTC
This is fixed in 5.3beta2, but not in 5.2.4.2.
Reverse bibisect results with bibisect-linux-64-5.3 repo (bisected to single commit):

https://cgit.freedesktop.org/libreoffice/core/commit/?id=2ad50c9a8c8411a57bbbd7a52734e72ffc4cc0ee

author	David Tardon <dtardon@redhat.com>	2016-11-22 08:07:54 (GMT)
committer	David Tardon <dtardon@redhat.com>	2016-11-22 20:37:17 (GMT)

"avoid loss of text in edited placeholder
How to reproduce:
1. Create an empty presentation.
2. Save it.
3. Click at one of the text placeholders and write something.
4. Save again.
5. Reload. The placeholder is missing. (Actually, it's still there, but
   empty and 0-size.)

This only happens if a11y is enabled."

Needs backporting to 5.2 branch.
Comment 5 Commit Notification 2017-01-04 19:59:58 UTC
Jan Holesovsky committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=6106fea591f685bc1fd5b65ade86e2e45dbc58e1

tdf#81754: Unit test for the loss of text on save of pptx.

It will be available in 5.4.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 6 Aron Budea 2017-01-04 20:23:36 UTC
David, could you backport your commit identified in comment 4, which fixes this bug to 5.2? Thanks!