Version: 1.13.5 (using KDE 4.5.0) OS: Linux After upgrading to KDE 4.5 from 4.4.x the automatic spellcheck while typing a message in composer has stopped working. I have it turned on (Options | Automatic Spellchecking). Reproducible: Always Steps to Reproduce: Turn it on: Options | Automatic Spellchecking. Actual Results: Doesn't work. No misspelled words are marked. Expected Results: Should mark misspelled words.
I have absolutely the same problem, if there is an solution it would help very mutch
Bug #248471 "Automatic spellchecker doesn't underline misspelled words." seems to be a duplicate of this bug. I can add that "Auto Spell Check" does work: i.e when I right click misspelled word I receive suggestions how to correct it but it is not underlined. I noticed that when I go to: Settings -> Spellchecker... and click "OK" underlining is restored.
A more permanent solution than the suggested by Andrzej is going to "System Settings -> Locale -> Spell Checker" and tick "Automatic spell checking enabled by default" which is not enabled by default. Kmail seems unable to override the default system setting unless its forced to do so by following Andrzej procedure *in each mail written*. Simply disable the system wide option to confirm this.
*** Bug 248471 has been marked as a duplicate of this bug. ***
*** Bug 250539 has been marked as a duplicate of this bug. ***
yes Comment #3 From Andres Blanc solved it for me. I do think Automatic spell checking should be enabled by default in global setting or Kmail should be able to override the default system setting for spelling (for all mails and note case by case)
Indeed this solution to change the global settings solved the problem with me. It seems that KMail does not override these. What is interesting tough is that I have only English installed in the global settings while using three languages in Kmail -- all work fine now without any interference from two of them not being set in the global settings.
You will have to excuse me as my english parser is more broken than usual at the moment. To be (perhaps) clearer: A simple bug in Kmail's startup code seems to forget calling whatever function(s) overrides this global setting. Clicking "ok" in the dialog outlined at #2 simply forces such function(s) call. jms, I don't think it is an ideological choice by the developers (if that is what you meant). Also, I don't know how Kmail or its editor is engineered but this might be a Sonnet bug rather than a kdepim bug. Admins should keep that in mind.
As I've written before: It is a problem of VISUALIZATION. When I right-click misspelled word I receive suggestions how to correct it but it is not underlined. So spellchecker IS working but it simply doesn't underline misspelled word.
(In reply to comment #9) > As I've written before: > > It is a problem of VISUALIZATION. > > When I right-click misspelled word I receive suggestions how to correct it > but it is not underlined. > > So spellchecker IS working but it simply doesn't underline misspelled word. Yes as you said before the spellchecker works but does not highlight misspelled word. But why changing the global setting as in Comment #3 From Andres Blanc turn back on the misspelled words highlighting?
(In reply to comment #10) > > Yes as you said before the spellchecker works but does not highlight > misspelled word. > But why changing the global setting as in Comment #3 From Andres Blanc turn > back on the misspelled words highlighting? As an interim solution, that works. As a permanent solution, it makes no sense. This should be an application-level setting and feature. To have to enable this on a system level to get an application to behave appropriately is not a good fix. I hope the dev team will understand that and apply the appropriate fix.
I'm using KMail 1.13.5 in Kubuntu 10.10 with KDE 4.5.3 and I'm experiencing this bug too, but none of the fixes work. If I start typing, a red line appears under the word, but vanishes as soon as I press space if the word is spelled correctly or not.
Also doesn't seem to be working with Choqok and Kopete, but it is working with KWrite.
I too have this bug and Andres's workaround works for me as well. That said, is there any news on getting this bug fixed the right way? It's been over 8 months...
*** This bug has been marked as a duplicate of bug 247486 ***