Bug 130443

Summary: 6.4 screwed up all footnotes created in previous version
Product: LibreOffice Reporter: larrybradley <larrywbradley>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: raal
Priority: medium    
Version: 6.4.0.3 release   
Hardware: All   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 103164    

Description larrybradley 2020-02-05 00:20:53 UTC 
Description:
Installed 6.4 then opened file created in 6.3. Screwed up all my footnotes, placed them in the regular text area and botched up the numbers in the text connected to the footnote. After fixing, the footnote separator bar went away and could not be restored even though the Page settings are set for the separator.

Steps to Reproduce:
1. Installed 6.4 to replace 6.3
2. Opened Writer file created in 6.3. Document contained footnotes.
3.

Actual Results:
Footnotes separator went away and footnote numbers were garbledl.

Expected Results:
Expected footnotes to remain the same as they were in previous version of LO. 


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 raal 2020-02-05 01:26:42 UTC 
Hello,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Thank you
Comment 2 Timur 2020-02-25 12:30:21 UTC 
Please send sample as requested.
Comment 3 Dieter 2020-04-21 07:22:05 UTC 

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