[SOLVED] Issues with enchant-2.6.6 and evolution-3.50.1

fskmh · 02-06-2024, 01:25 PM

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 fault

If 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))
Aborted

After 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?

reddog83 · 02-06-2024, 07:50 PM

I am getting this as well on Slackware Current with Gnome 45

Quote:

(evolution:7819): GLib-WARNING **: 19:51:56.540: 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/nathan/.config/enchant/hunspell”: No such file or directory
Segmentation fault

reddog83 · 02-06-2024, 10:19 PM

Well talking with some people on a matrix channel one of the guys mentioned that it looks like the bug is in this commit: https://github.com/AbiWord/enchant/c...1de31253ab4d12

jloco · 02-06-2024, 10:44 PM

I just built evolution on current (after removing any/all deps centering on optional Microsoft Outlook integration) and it operates just fine. Checked and I have enchant-2.6.6/hunspell-1.7.2 installed, so this has to be caused by something else.

fskmh · 02-07-2024, 01:37 AM

Quote:

Originally Posted by jloco

I just built evolution on current (after removing any/all deps centering on optional Microsoft Outlook integration) and it operates just fine. Checked and I have enchant-2.6.6/hunspell-1.7.2 installed, so this has to be caused by something else.

Unfortunately, the support for Exchange and EWS is the only reason I use this mail client.

jloco · 02-07-2024, 02:35 AM

Quote:

Originally Posted by fskmh

Unfortunately, the support for Exchange and EWS is the only reason I use this mail client.

EWS support is handled by the 'evolution-ews' plugin which is a separate SlackBuild from evolution itself. For my build I removed the deps on libpst, ytnef, and uhttpmock, as they include features for handling Outlook attachments and data (which I don't personally need). If it's EWS you're after, that at least appears to build fine, but operation I can't verify, as I don't use Exchange. But evolution does start with the EWS plugin installed for me locally, with a up to date current system and evolution 3.50.3.

I am curious if reddog83 got anywhere with this issue, as it seems you both meet the criteria for it to happen and I don't, I'm wondering if it's from one of the deps I omitted...

fskmh · 02-07-2024, 03:05 AM

Yes, I'm using all three of those and then some. Upgraded evolution-data-server, evolution and evolution-ews from 3.50.1 to 3.50.3 in case I was missing a bugfix, but the issue persists with enchant-2.6.6.
Here's my build tree fwiw:

Code:

001-unifdef
002-libwpe
003-wpebackend-fdo
004-libavif
005-xdg-dbus-proxy
008-highway
009-libjxl
010-webkit2gtk
012-libadwaita
013-gtksourceview5
014-rest
016-gspell
020-highlight
030-libpst
031-libmspack
032-cmark
033-uhttpmock
034-geocode-glib
034-geocode-glib2
035-libgweather
036-gnome-online-accounts
037-liboauth
038-libgdata
047-evolution-data-server
048-syncevolution
049-cogl
050-clutter
051-clutter-gtk
052-libchamplain
053-gnome-autoar
055-ytnef
060-evolution
061-evolution-ews

DryFalls · 02-07-2024, 03:39 AM

Only half off topic: same error as op shows with epiphany (SBo) although other browsers (MiniBrowser, surf) using webkit2gtk (4.0 & 4.1) are unaffected.

fskmh · 02-07-2024, 04:55 AM

Submitted issue to upstream on github:
https://github.com/AbiWord/enchant/issues/356

jloco · 02-07-2024, 10:23 AM

Quote:

Originally Posted by fskmh

Yes, I'm using all three of those and then some. Upgraded evolution-data-server, evolution and evolution-ews from 3.50.1 to 3.50.3 in case I was missing a bugfix, but the issue persists with enchant-2.6.6.
Here's my build tree fwiw:

I've attached a sboui screenshot of my deps according to my personal repo. I'm about to built it again, after having updated to the latest current changes here to see if I encounter the bug on aarch64 or not. Just taking shots in the dark... for science.

marav · 02-07-2024, 10:37 AM

For what it's worth

Code:

The --with-hunspell-dir configure option is removed (along with all the
other ---with-PROVIDER-dir options, which did nothing). Users who have
Hunspell dictionaries in non-standard locations should set the
Hunspell-specific environment variable DICPATH, or copy the dictionaries
into their user’s Enchant configuration directory (for example
~/.config/enchant/hunspell).

https://github.com/AbiWord/enchant/blob/master/NEWS

sombragris · 02-07-2024, 10:46 AM

I use claws-mail and I also got bitten by this bug. The app starts just fine but whenever I try to reply to an email it segfaults with this message. Tried to reinstall hunspell and enchant, and rebuild claws-mail, to no avail. Reverting to enchant-2.6.5 fixes the issue.

marav · 02-07-2024, 10:58 AM

So, let's hope the maintainer fixes the reported issue ;-)

reddog83 · 02-07-2024, 03:09 PM

Problem fixed by reverting to enchant 2.6.5 in latest changelog

fskmh · 02-08-2024, 03:02 AM

Marking as "solved" since this is no longer an issue with Slackware itself.

Update: Built, installed enchant-2.6.7 and evolution starts up like it did with 2.6.5.