Description: Following update to LO 7.1.1.1 on Ubuntu 21.04 the autocorrect function stopped working completely. Resetting everything, even wiping the install and reinstalling doesn't correct it. It does not replace anything, nor will it correct two initial capitals or capitalize the first letter of a sentence. Steps to Reproduce: 1.type anything that should be corrected such as "TRacy said hello." It will not correct. 2. 3. Actual Results: Highlighted as error Expected Results: should have autocorrected to "Tracy said..." Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.1.1.1 / LibreOffice Community Build ID: 10(Build:1) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.1.1~rc1-0ubuntu0.21.04.1~lo2 Calc: threaded
So you mean, you reproduce this on a brand new file and with a clean LO profile? (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)
Thank you for reporting the bug. I can't reproduce this bug in Version:7.1.0.3/LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 1; OS:Linux 5.8;UI render:default; VCL; gtk3 Locale: en-US (en_US,UTF-8);UI:en-US Calc:threaded Also in Master Build Version:7.2.0.0.alpha0+/LibreOffice Community
Due to the frequent auto updates, I'm currently up to the following version of LO. And yes, it happens in a new document with a clean profile. It's still happening. Version: 7.1.1.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.1.1~rc2-0ubuntu1 Calc: threaded
Hello, I cannot reproduce this bug in Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
I can't reproduce. Could you try with 7.3? Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 66a9795f27fda887d9f66d0d8bb196fd636fe452 CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 7 March 2022 Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear hippie.hippo, 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
Dear hippie.hippo, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp