Since it is a bug in Ubuntu's Seamonkey package, and not in Seamonkey itself, the bug rightfully got an "invalid" state. However, the person who marked it as "invalid" also gave a possible reason for the bug:
> Invalid => Downstream problem. Probably Ubuntu are shipping a newer version of
> the Hunspell libraries which SeaMonkey 2.0.x isn't designed to work with.
This bug was also reported to Mozilla's Bugzilla: /bugzilla. mozilla. org/show_ bug.cgi? id=653914
https:/
Since it is a bug in Ubuntu's Seamonkey package, and not in Seamonkey itself, the bug rightfully got an "invalid" state. However, the person who marked it as "invalid" also gave a possible reason for the bug:
> Invalid => Downstream problem. Probably Ubuntu are shipping a newer version of
> the Hunspell libraries which SeaMonkey 2.0.x isn't designed to work with.
Not sure if this helps.