Description: I can add a Table of Contents at the END of the document, but if I add it to any other place in the document writer freezes upon clicking the OK button of the "Insert Table of Contents" dialogue. I made a pretty standard document from scratch. There is a simple title page, then a table of contents, figures index and tables index. Started to write, all worked well, indexes updated without problem. When I finished the 55 pages document, i wanted to update the indices, and then noticed there was a yellow triangle visible in the context menu of the table of contents, clicked update, document froze. Ok restart, recover document, deleted the ToC, wanted to reinsert, and since then writer freezes when clicking the ok button of the ToC insert dialogue. I played around for hours, went back to stable version of LO, reinstalled, started in safe mode, changed headings, deleted unused styles, removed direct formatting, checked all styles, deleted parts of the document content for testing, modified the options of the ToC insert dialogue, changed settings in the user profile (JAVA), nothing helped a bit. I found out I can add a ToC at the End of the document, but everywhere else the ToC dialogue freezes as described. I use LO for a few month now and am incredible frightended to use this software further. Its inherently unstable, and gives not the slightest hint what might be wrong in the document, it simply freezes forever. If this would have been an imported / converted document with difficult arrangements I could possibly understand, but I made a standard document with 2 levels of headlines, header, footer, titlepage, ToC, ToF, ToT, tables, bullet lists, images. Really nothing fancy at all. And all was made from scratch without "importing" some difficulty via the clipboard, no direct formattings, all styled - and still this program hangs. This is terrifying as obviously the mere basics of LOW simply do not work. Steps to Reproduce: 1. open ToC dialogue to insert ToC on any other than the last page. 2. Click enter on the ToC dialogue Actual Results: Writer freezes. Need to close the program. Windows report the program as not responsive - you wanna wait or terminate? Terminate. Expected Results: Open the document again, which then recovers it successfully. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.2.3 (x86) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (de_AT); UI: en-US Calc: threaded I tried with ampty new documents, and with other documents. ToC was not the issue there, so this clearly is something in my document, which - as described - could be used as an example for editing LO docs.
Would it be possible you attach the document here so we can give it a try? (of course, don't forget to sanitize it before attaching the doc, see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)
Hi, thanks for the fast response. I tried to sanitize the document as described in https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission Two massive bugs again: 1) regular expression change of all characters fails! I used "." as the regular expression without quotation marks. And replaced by an x. Additionally I chose format - the only font used in all document and "regular" to preserve all captions which are in italic (nothing else is italic in the document). This did NOT replace all characters but kept several paragraphs in its original form, while they fully and entirely matched the search parameters. Same font, same font attributes, same style as others, no direct formatting. 2) When I want to save the changes, LO writer again freezes. So, sad to say that I cannot provide the file as this is extremely sensitive. I am really worried whether changing to LO was a good move and I need to go back to MS Office. LO is terribly unstable and full of bugs, a nightmare and I am almost shocked that this has version 7 while being in fact a beta version. Is there no log file, no debug file, not the slightest support for recording failures, or debugging them? How ever do you want to make a software stable without such features? However, I think it does not make sense to continue this bugreport. Thanks.
If you've got some time, you can try https://wiki.documentfoundation.org/QA/FirstSteps Concerning debugging, you can try https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
Thanks, I am not capable to do debugging. I meant some log files that would help identify the issue. Obviously there is no such debug info in LOW that could be sent to developers for identifying the issue. This lack of debug/diagnosis information kind of explains why a trivial task for a writer program such as adding a table of contents does not work in Release 7 of a program. I will now go back to MS Word, LibreOffice Writer just crashed another of the documents I am working on. When saving it hangs and freezes at "Repagination" being displayed in the status bar. I had not made significant changes, just deleted some blanks, and applied a style to a paragraph. After 40 mins of waiting LOW is still frozen and can only be terminated. No trace, no debug file, no error message, no nothing except for an empty tmp file on the disk. I programmed some 20 years ago and even then it was usual that an exception is thrown, debug info stored.LoW 0. A truly shocking day, as I was hoping to convert to FOSS and put month and many hours into learning and converting. I really cant understand how such a crap software is even being advertised as usable.
About logs, I can't tell since I use LO mostly in Linux and I launch LO from console to see when I got a buggy behaviour to see errors. Perhaps there may be some infos in eventviewer. I confirm it's quite shocking that a dev with 20 years exp : - doesn't distinguish retrieving extra info using a provided link from debugging the bug - doesn't try to reproduce the TOC crash with a brand new doc, 1 page of Lorem Ipsum just to know if the TOC pb just reveals a pb but perhaps it's not the root cause Now if you're happy with MsOffice, just use it, no pb here.