Summary: | Crash when opening composer with dictionary language set to nb | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Kjetil Kjernsmo <kjetil> |
Component: | kspell | Assignee: | Zack Rusin <zack> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | cfeck |
Priority: | NOR | ||
Version: | 4.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Kjetil Kjernsmo
2009-11-03 11:27:23 UTC
Looks more like a Ispell issue to me. Reassign to kspell. You would get a better backtrace after installing the debug package for kdelibs. Now I remember that Norway had two "languages" (no and nb?), so maybe there is some internal remapping and something fails. I would suggest to try other languages (I understood that english is fine), and if it only happens with "nb", then maybe ask ispell or enchant maintainers what the reason could be. At least, report this bug to the ispell team, as the crash is deep inside ispell. Sorry, I mean report that to the enchant team, it is the ISpell "plugin" for enchant that crashes. You can find them at http://www.abisource.com/projects/enchant/ Thanks a lot for the quick response. It seems there is a very similar issue with Evolution in the recent Ubuntu release, and there is a bug report for it: https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/463920 I have some problems getting the package with debugging symbols for enchant installed, but I'll try to get a report prepared for Ubuntu and for the developers. Indeed, we are in a somewhat messy situation here with two different but similar written languages, nb and nn, and they are also denoted no. I tried to set the default to no, but it didn't help. Anyway, I'll mention it in my report. OK, on closer inspection, it appears to be unrelated to the Evolution bug. I have created a new Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/474062 and sent the Enchant developer an email about it. You were right, this was a bug in enchant, and the developer has fixed it now. I have built a package for myself and kmail works reliably again. So, closing as invalid. |