Bug 457847 - Unable to add word to dictionary, language settings are broken
Summary: Unable to add word to dictionary, language settings are broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-04 22:35 UTC by Christopher Beland
Modified: 2018-04-11 09:39 UTC (History)
2 users (show)

Fixed In Version: evolution-2.24.0-1.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-19 04:01:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Christopher Beland 2008-08-04 22:35:32 UTC 
While composing an email, I see a red squiggly line under the word "Beland" to indicate that it is misspelled.  I right-click on this word and select "Add Word to Dictionary".  I get an error dialog box that says, "Unable to add word to dictionary, language settings are broken."  This is with evolution-2.22.3.1-1.fc9.i386.
Comment 1 Matthew Barnes 2008-08-05 03:30:57 UTC 
Unlikely this is going to get fixed in Fedora 9 at this point.

In Fedora 10 (Rawhide) Evolution's spell checking has been completely rewritten. Could you try testing this on Evolution 2.23 (or the yet-to-be-released 2.24), whenever you get around to installing it?
Comment 2 Matthew Barnes 2008-08-05 03:32:48 UTC 
Grrr.  What the heck happened to the NEEDINFO status in the new Bugzilla?
Comment 4 Matěj Cepl 2008-09-18 15:48:35 UTC 
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 5 Christopher Beland 2008-09-23 15:03:26 UTC 
I downloaded and ran the Fedora 10 Alpha LiveUSB release today; this bug is fixed in that release.  Oddly, it appears to be Evolution 2.22.1.
Comment 6 Matthew Barnes 2008-12-19 04:01:47 UTC 
Closing as fixed per comment #5.  Thanks for the update.
Note You need to log in before you can comment on or make changes to this bug.