Description: I just experienced a series of Writer crashing, anonymous report starting from UUID: 27bd50d1-04d4-4b38-a70b-8f31ca3b6fa0, all the same system information: Version Version: 6.1.1.2 OS linux OS details 0.0.0 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 Build Architecture amd64 CPU Info family 6 model 69 stepping 1 Crash Reason SIGSEGV Crash Address 0x621600004e9d Crash Thread 0 All the crashes happened during I re-format the long multi-layered numbered list in the first column of the second table. The display (rendering) "bumped" every time I changed a line, then after some time it crashes. After trying hard to make things done, saved and reopened, and tried to re-organize the numbered item, the layer will become mis-ordered. (Desktop recording attached later) Steps to Reproduce: 1. Open the odt file. 2. In the second table, around item (八)、(九)、(十), put the cursor in front of (九), hit the Backspace to attached after the item (八), then hit Enter to go back. 3. Do the same to (十) to attached after the item (九), then you can see the numbered 7. (under (七)) became mis-ordered. Actual Results: Item (七） 7. became mis-ordered. Expected Results: Item (七） 7. should stay where it was. Reproducible: Always User Profile Reset: No Additional Info: It looks like something not handling well with long, multi-layer numbered list positioned in a table. The original file is a .doc file, but I cleared all the format before re-formatting, set up the numbered list properties, then did the re-format.
Created attachment 145425 [details] Problematic odt file Please try with this odt file.
Created attachment 145426 [details] The original doc file For reference. I opened this file with LibreOffice 6.1.1, cleared all the format, and then saved as odt file then re-formatted it.
Created attachment 145427 [details] Desktop recording
Repro while doing the same steps as in the video. In my case it was 6. that moved. I cannot repro on Windows. I did not repro with Linux 50max bibisect repo. By the way, if you undo back to the beginning, do you get a crash? In 6.2, having experimental features enabled, the document crashes on opening. I suspect it will be fixed with https://bugs.documentfoundation.org/show_bug.cgi?id=120991#c9 Arch Linux 64-bit Version: 6.2.0.0.alpha1+ Build ID: 45d8fb0ba77396b7d5e02c2fc9a8ae5b233a02bc CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on 31 October 2018
Dear Franklin Weng, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The original bug is not reproducible in: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 9e8c1da64fa8a520730ce0aea0f7199cd75c892f CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded However, after I press the backspace, and ENTER key, I do not get back the numbering. I have to press the ENTER key twice to get the Chinese numbering, but this creates an empty line as well.
Dear Franklin Weng, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I could not reproduce in: Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I followed the steps in comment 3's video exactly. I think the initial "crash" / "7. appearing" issue is fixed, but there ARE a few other oddities with attachment 145425 [details]. - - - ODDITY 1: BACKSPACE + ENTER (Twice) Like Ezinne in comment 6 said, you have to "press ENTER twice" to get the auto-numbering to show back up: 0. Open attachment 145425 [details]. 1. In the second table, put the cursor right: - After "(九)" - The Chinese auto-numbering. - Before "廠商於協商後重行遞送之". 2. Press BACKSPACE once. - Auto-number disappears. 3. Press ENTER once. - Auto-number appears, but extra line added above too. so the lines looks like this during Step 1: > 之廠商，並作成協商紀錄。 > (九) 廠商於協商後重行遞送之 and this after Step 3: > 之廠商，並作成協商紀錄。 > > (九) 廠商於協商後重行遞送之 - - - If you do: 2. Press BACKSPACE twice. 3. Press ENTER twice. you get: > 之廠商，並作成協商紀錄。 > (九) 廠商於協商後重行遞送之 and this after Step 3: > 之廠商，並作成協商紀錄。 > (九) > 廠商於協商後重行遞送之 - - - In Step 3, you use UNDO (Ctrl+Z), everything resets fine: 0. Open attachment 145425 [details]. 1. In the second table, put the cursor: - After "(九)" - The Chinese auto-numbering. - Before "廠商於協商後重行遞送之". 2. Press BACKSPACE once or twice. 3. Press Edit > Undo (Ctrl+Z) once or twice. - - - ODDITY 2: COPY/PASTE On page 6/7, I copied everything down from "6." down to the end of "(九)"... but it seems like LO pastes the wrong numbers! For example, this is what it looks like in the ODT document: > 7. 工作小組擬具初審意見及評選委員會審查、議決等評選作業，是否以記名方式秘密為之。 >(八) 是否善用協商程序，以避免價格不合理、浪費公帑之情形。協商時是否平等對待所有合於招標文件規定之廠商，並作成協商紀錄。 >(九) 廠商於協商後重行遞送之投標文件，其有與協商無關或不受影響之項目者，該項目是否不予評選，並是否以重行遞送前之內容為準。 but when I paste that into Notepad++, I get: > 14. 工作小組擬具初審意見及評選委員會審查、議決等評選作業，是否以記名方式秘密為之。 >(十六) 是否善用協商程序，以避免價格不合理、浪費公帑之情形。協商時是否平等對待所有合於招標文件規定之廠商，並作成協商紀錄。 >(十八) 廠商於協商後重行遞送之投標文件，其有與協商無關或不受影響之項目者，該項目是否不予評選，並是否以重行遞送前之內容為準。 Notice the auto-numbers are all wrong: - 7 -> 14 - 八 -> 十六 - 8 vs. 16 - 九 -> 十八 - 9 vs. 18 It *seems* like LO 24.2 is: - visually "counting by 1s" - accidentally "counting by 2s" underneath