Summary: | evolution 1.3.x crash on new mail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Link M Dupont <link.dupont> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Link M Dupont
2003-05-09 18:23:54 UTC
experiences on other platforms with old versions of applications under heavy development are no guarantee for the future. I assume you have a dictionary installed ? Get us a backtrace of the crash, with debugging enabled if you can (recompile with 'debug' in USE ). gnome-spell is not linked but activated via bonobo. i assume you are using gnome-spell-1.0.3? what happens if you actually set the composer dictionary language in evolution's settings? looks like a gnome-spell thing more than a evolution thing. *** Bug 20728 has been marked as a duplicate of this bug. *** OKay, taking Alistair's recommendation in, it worked okay. Sorry for posting this thing twice, i must've hit reload or something. Any ideas why this wasn't turned on by default? hmm .. i never had it crash when i didn't have my dictionary language set. it just didn't turn on spellcheck rather than crash evolution. there must be something funny with the GConf keys that it was expecting. i can't reproduce this at all though, because gnome-spell automatically generates those keys. maybe your gconf keys (especially /GNOME/Spell/language) were corrupted. but removing the actual key doesn't cause it to crash. if you could provide some more insight into how to reproduce this then we can get somewhere, otherwise it "worksforme". i really have no clue how to reproduce this. My GConf keys in /Gnome/Spell seem okay to me. language = en-US, etc. My only guess is that environment variables weren't set. Possibly LANG, or something like that. I've had issues on Gentoo with that in the past. But other than that, I don't have a clue why/how that happened. well, can't find a solution to this. i'll try probing ximian about it. although the fact i can't reproduce it will be a problem. ok. i'm now able to reproduce this. and the REAL solution is the have LANG environment variable. eg: export LANG=en_US i've filed a bug with ximian and see if they'll try and handle this gracefully rather than crashing |