Bug 54040 - No Spell Check
Summary: No Spell Check
Status: RESOLVED DUPLICATE of bug 53006
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-25 07:56 UTC by Peter
Modified: 2012-09-18 05:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2012-08-25 07:56:56 UTC
Libre Office was getting really usuable - now spelling does not check.  
I previously was able to use Australian English without problem.

The previous version was ok I think.

Guys say if something won't work, so we can all save band width.

Peter Schnell
Comment 1 billhook 2012-08-26 08:13:49 UTC
This was a known issue with 3.6.0.4. From the release notes:

http://www.libreoffice.org/download/release-notes/

"If you update from an earlier version, spellchecking might be broken. In this case, the following workaround helps:

    On Linux, in a terminal window enter "rm -r ~/.config/libreoffice/3/user/extensions"
    On Mac OS X, in a Terminal window enter "rm -r ~/Library/Application\ Support/LibreOffice/3/user/extensions"
    On Windows, in a Command Prompt window enter "rmdir /q /s %appdata%\LibreOffice\3\user\extensions"
    After that, please restart LibreOffice twice."

Does this fix your issue?
Comment 2 Rainer Bielefeld Retired 2012-09-18 05:31:33 UTC
I think this one is more or less a DUP of "Bug 53006 - Autocorrection TWo
INitial CApitals does not work because of bundled extensions problem", root of
the problem is incorrect update for "bundled extensions"

@Reporter:
please feel free to reopen this Bug if you find evidence that we have an
independent issue here. Indicator might be that renaming of folder "bundled"
under "extensions" in User Profile
<https://wiki.documentfoundation.org/UserProfile#User_profile_location>
does not heal your problem.

*** This bug has been marked as a duplicate of bug 53006 ***