Created attachment 190958 [details] Backtrace of soffice crash when deleting a blank entry in AutoCorrect This bug was filed from the crash reporting server and is br-bde09805-3baf-42ce-b98e-a179d979f861. ========================================= 1. Tools > AutoCorrect > Options > [Replace] Tab 2. Found a blank entry some way down in the same row in both the [Replace] and [With] columns 3. Clicked [Delete] 4. (paraphrase) KDE Crash Handler reported soffice had closed suddenly and could not automatically report same as the crash handler lacked the necessary address. 5. Saved the backtrack file and attaching here. Actual Results: LO crash. Expected Results: LO to not crash. Reproducible: Yes, in normal mode 1. Tools > AutoCorrect > Options > [Replace] Tab 2. Found a blank entry some way down in the same row in both the [Replace] and [With] columns 3. Clicked [Delete] Repeated Actual Results: LO crash. LO takes up to 3 minutes to open after crash. Reproducible: No, Not in safe mode. 1. Tools > AutoCorrect > Options > [Replace] Tab 2. No Blank entry is found in the same row of both the [Replace] and [With] columns User Profile Reset: No Attachment: Kcrash backtrace File: soffice-20231122-015033.kcrash LibreOffice information: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 24; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Platform information: Operating System: Ubuntu Studio 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-lowlatency (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: NV172 Manufacturer: MicroElectronics Product Name: G905 System Version: 1.0
Created attachment 190960 [details] The LibreOffice crash capture information pop-up
I don't have blank entries in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6f227b0dd912d4c70a01eb3872fff15d52de543a CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: x11 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded Is there any way to create the blank entries from scratch ?
Dear L P Luigi Espenlaub, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Did not mean for this length of delay I am currently on the same version and build Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 Now I see my - * Expected Result should have been "Not to find a blank line in the list." * Actual Result better described as: "finding an empty line in the list." As to your question "Is there any way to create the blank entries from scratch ?" I think not, the blank line was just there in the list and a surprise. At the time with that line selected both the replace and with fields above the list were blank, but the [Delete] button was live, that is clickable. Clicking it was what created the crash and notice. 1. I just now scrolled through the entire replace-With list and find blank line formerly found between :zzz: and the alpha entries, thankfully, is now missing. 2. Now when both the 'replace' and 'with' fields above the list are blank, both the [New] & [Delete] buttons are grayed out as should be. 3. Since there is no longer the ability to click [Delete] when both fields are empty, the crash cannot be repeated. 4. These changes have resolved the problem.