This bug was filed from the crash reporting server and is br-2105dfa8-ba3c-402a-af32-d88d645e5d7d. ========================================= Creating a new file with a title and about half a dozen Heading 1 lines, I inserted a table of contents near the top (playing with some options to see what they did to the preview but settling on a default TOC with one level) then selected one of the headers and tried to drag it up the document. On releasing the button the program crashed. On re-starting, automatic recovery took me back to before I had inserted the table of contents; repeating the insertion and subsequent drag-and-drop everything worked fine.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
As noted in the initial report, the recovered file didn't cause a crash when I tried repeating the operation. I have subsequently tried recreating the file from scratch but have not been able to reproduce the crash. I do recall messing with various settings on the TOC but not exactly what I did, only that I undid every change apart from reducing the levels to one. Sorry not to be more helpful.
Hello Andrew, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
I'm afraid I was never able to reproduce the bug. I had hoped you might be able to do something with the crash report, but if not I guess we'll have to wait until somebody comes across the bug in a more reproducible context.
(In reply to Andrew Fisher from comment #4) > I'm afraid I was never able to reproduce the bug. I had hoped you might be > able to do something with the crash report, but if not I guess we'll have to > wait until somebody comes across the bug in a more reproducible context. Hello Andrew, unfortunately the information at hand is not enough to investigate the issue. Let's close it as RESOLVED INSUFFICIENTDATA for now. Thanks for reporting it anyway.