Issues with enchant-2.6.6 and evolution-3.50.1
by fskmh from LinuxQuestions.org on (#6JE83)
Question for other Slackers running evolution mail client using their own SlackBuilds...
I just noticed today that since the -current Feb 5 upgrade to enchant-2.6.6 I get this error when running evolution:
Code:(evolution:15332): GLib-WARNING **: 21:10:24.536: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Error opening directory /home/user/.config/enchant/hunspell": No such file or directory
Segmentation faultIf I create the missing directory I get this error:
Code:**
ERROR:enchant_hunspell.cpp:300:char* hunspell_request_dictionary(const char*): assertion failed: ((dir == NULL && err != NULL) || (dir != NULL && err == NULL))
Bail out! ERROR:enchant_hunspell.cpp:300:char* hunspell_request_dictionary(const char*): assertion failed: ((dir == NULL && err != NULL) || (dir != NULL && err == NULL))
AbortedAfter downgrading to enchant-2.6.5, evolution starts up like it used to. I'm using the stock Slackware hunspell and enchant packages. I built enchant-2.6.5 and enchant-2.6.6 myself from sources and I get the same result. If there is a null pointer error emanating from hunspell, I'm not seeing any diffs or patches for it, so is it just me or is someone else also getting this error?
I just noticed today that since the -current Feb 5 upgrade to enchant-2.6.6 I get this error when running evolution:
Code:(evolution:15332): GLib-WARNING **: 21:10:24.536: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Error opening directory /home/user/.config/enchant/hunspell": No such file or directory
Segmentation faultIf I create the missing directory I get this error:
Code:**
ERROR:enchant_hunspell.cpp:300:char* hunspell_request_dictionary(const char*): assertion failed: ((dir == NULL && err != NULL) || (dir != NULL && err == NULL))
Bail out! ERROR:enchant_hunspell.cpp:300:char* hunspell_request_dictionary(const char*): assertion failed: ((dir == NULL && err != NULL) || (dir != NULL && err == NULL))
AbortedAfter downgrading to enchant-2.6.5, evolution starts up like it used to. I'm using the stock Slackware hunspell and enchant packages. I built enchant-2.6.5 and enchant-2.6.6 myself from sources and I get the same result. If there is a null pointer error emanating from hunspell, I'm not seeing any diffs or patches for it, so is it just me or is someone else also getting this error?