Description: LibreOffice Writer Version: 5.2.0.4 Build ID: 066b007f5ebcc236395c7d282ba488bca6720265 CPU Threads: 2; OS Version: Linux 3.13; UI Render: default; Locale: en-US (en_US.UTF-8) working under Ubuntu 14.04 LTS 32 bit system The subject file is a large file the bulk of which has been put into a section so as to places the indices at the end of the file beyond the endnotes. Problem: Index markings made during a current editing session are erased at closing. An index created during a current editing session is loaded, but updates to a blank index. Possibly related problem: Status bar does not appear on command. So far as I can tell, this problem is specific to this file. Steps to Reproduce: 1.Load file 2.Create an index category and enter an index marking under the new category 3.Page to area beyond the endnotes. 4. Create the new index 5. Close file. 6.Open file. 7. Index markings have disappeared! 8. In index at the end of the file appears, but upon update becomes blank. 9. Possibly related. the status bar commanded under View, sometimes fails to appear. Actual Results: All index markings have been erased from the file. Updated indices return blanks. Expected Results: Index markings will perdure. Status bar will appear on command. Reproducible: Always User Profile Reset: I have in the past to no effect, but I will try again. Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:49.0) Gecko/20100101 Firefox/49.0
I,ve updated the user profile, but the problem persits
Created attachment 128206 [details] This is a tial file which shows the problem The attachment is a small file to illustrate the problem. A section has been created with line of text and a couple of endnotes. The section is colored white so it can be distinguished from the main body of text. The section is followed by a a page for an index. The index (Trial)is created. When the file is closed and then reopened, the index markings are lost, but the Trial index appears. Updating the index causes the index content to disappear.
*** This bug has been marked as a duplicate of bug 100182 ***