Created attachment 115456 [details] Document created from right-click context menu in explorer Hello, When I have a folder open in Windows Explorer, and I right-click in the folder to pull up the Windows context menu, and choose "New->OpenDocument Text" to create a Writer document, when I go to edit that document, neither Automatic Spell Checking, nor Tools->Spelling And Grammar work. Spelling And Grammar tells me that the document is fine, that there are no errors. I've tested this on a document filled with absolute nonsense. However, everything works as expected if I create a new document from the LibreOffice Writer menu. Windows 7, 64-bit. LibreOffice 4.4.3.2. I've attached an image showing that the autocorrect is active, and that a bunch of incorrect text is not underlined. Side-note: I came into the office today, created a new document, and the auto-correct issue suddenly appeared. Creating documents as described above is normal procedure for me, so this issue actually just appeared seemingly out of the blue. At the time, I was using a version of LibreOffice prior to 4.3.7, I don't remember which version though. When the issue arose, I upgraded to 4.3.7. The issue persisted through a reboot, and through deleting my LibreOffice folder under <User>/AppData. I decided to do a full uninstall of LibreOffice, and then install version 4.4.3.2. The problem persisted. HOWEVER, it wasn't until I had installed 4.4.3.2 that I noticed that there was no issue when creating a document from the LibreOffice Writer software. It is possible that the problem existed under the prior conditions, and is likely, but is unconfirmed.
Created attachment 115457 [details] Document created from right-click context menu in explorer. Spell check finds no errors
Reproduced. When created with context menu, it says [None] in the status bar for language. Have to click it and set lang for paragraph or Tools - Lang - For all text. Then spellcheck works. Win 7 Pro 64-bit, Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Locale: fi_FI
*** Bug 91421 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
*** Bug 105921 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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
I am unable to reproduce this bug, it works for me. However, this bug might be the same as this similar spellcheck malfunction that happens in a more narrow set of circumstances: https://bugs.documentfoundation.org/show_bug.cgi?id=140090 Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL
Yep, it worked for me Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded