Bug 124926 - LibreOffice 6.2.3 breaks text paragraph styling
Summary: LibreOffice 6.2.3 breaks text paragraph styling
Status: RESOLVED DUPLICATE of bug 123054
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-24 09:31 UTC by Marcus Tomlinson
Modified: 2019-04-24 09:56 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Formatted document (760.41 KB, application/vnd.oasis.opendocument.text)
2019-04-24 09:32 UTC, Marcus Tomlinson
Details
Document open in 6.1.5.2 (1.29 MB, image/png)
2019-04-24 09:34 UTC, Marcus Tomlinson
Details
Document open in 6.2.3.2 (1.26 MB, image/png)
2019-04-24 09:35 UTC, Marcus Tomlinson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Tomlinson 2019-04-24 09:31:33 UTC
Description:
Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826052

After updating to 6.2.3 documents previously created in 6.1.5 have some of their paragraph styling wiped, e.g. a custom heading style was arbitrarily removed in some but not all instances in a document and was replaced with 'Default Style'.

(See attachments)

Steps to Reproduce:
1. Open the attached document in 6.1.5.
2. Open the same document in 6.2.3.

Actual Results:
Formatting broken.

Expected Results:
Formatting intact.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Marcus Tomlinson 2019-04-24 09:32:24 UTC
Created attachment 150967 [details]
Formatted document
Comment 2 Marcus Tomlinson 2019-04-24 09:34:33 UTC
Created attachment 150968 [details]
Document open in 6.1.5.2
Comment 3 Marcus Tomlinson 2019-04-24 09:35:04 UTC
Created attachment 150969 [details]
Document open in 6.2.3.2
Comment 4 Aron Budea 2019-04-24 09:56:11 UTC
This seems to be a duplicate of bug 123054, which means it's fixed, and the fix will be part of 6.2.4.

*** This bug has been marked as a duplicate of bug 123054 ***