Emerging aspell breaks gnome-spell-component and thus evolution spell checking. To reproduce: 1) have a perfectly working gnome-spell-component, with spell checking and highlighting misspelled words working in evolution's mail compose window. (latest versions of evolution 1.0.7, gnome-spell 0.4.1-r1, pspell-0.12.2-r3, pspell-ispell-0.12-r1, ispell-3.2.06-r1) 2) emerge aspell (aspell-0.33.7.1-r1) 3) aspell works fine if you use it by itself 4) try to spell-check something in evolution, it is broken. Stay in compose window, go to terminal and run /usr/bin/gnome-spell-component. Type another word in the body of the email, gnome-spell exits (no error, just cleanly exits) 5) unmerge & re-emerge evolution, gnome-spell, *spell, etc. Still broken 6) unmerge aspell. Then, you might need to recompile gnome-spell if you get an error about aspell libs. 7) everything works again. bad aspell. bad.
Recompiling gnome-spell is not necessary. Just remove aspell and the spell-checking in evo is working again.
You're right, that probably won't be necesssary usually. I had forgotten that in my quest to fix the problem, I tried re-compiling gnome-spell while aspell was still installed (hoping perhaps it would find aspell and then work just fine). Well, that didn't help, but when I then remoted aspell, gnome-spell wouldn't run, I assume because it was attempting to use the broken aspell (or its broken aspell calls). So, I recompiled without the presense of aspell, and then it worked.
what happens if you all choose a dictionary OTHER THAN aspell-en?
Right now it is set to "en". I've since upgraded to gnome2, and with aspell installed and gnome's html spell-checking language set to "en" it no longer does nothing. Instead, I can see the cursor quickly move through the entire email, then it says no errors found, even though I purposely included spelling errors. If I try aspell-en, ispell-en, etc. same thing.
hi lads, today I've commited an aspell-0.50-20020811 ebuild into portage. It is unmasked, but I would very much like you all to test it. Thanks,
Evolution now spell-checks properly after emerging that aspell ebuild. I'm fairly certain that evolution is using ispell though, and not aspell, since evolution has a child process named ispell and if I add a new word to my custom dictionary, it gets added to ~/.ispell_english. Next, I unmerged ispell (3.2.06-r5), and spell-checking no longer works in evolution. No words get underlined, but gnome-spell-component doesn't die as previously reported. If your goal was simply to not break evolution spell-checking when aspell is installed, then great work, its fixed. If you wanted aspell to actually work with evolution, then sorry but its still broke. I don't know which was the case, although I'd say having it not break evolution is great, provided that ispell is a dependency of the gnome-spell-component when people want spell-checking.
no, that was only partly my goal. my full goal was, of course, to make spell checking with aspell completely functional with evolution. to that end, I'm bringing leonardop to handle this with me.
sidenote on a tangent, my system cannot build abiword correctly with spellchecking enabled. I haven't filed a bug yet because my compiler's tagged as "EXPERIMENTAL" with big friendly letters across the side.
Is it necessary to recompile gnome-spell after I emerge aspell? I haven't tried that yet with the new aspell ebuild.
justin, please try the following (it seemed to work for me) unmerge aspell, pspell-ispell, pspell, and ispell then merge the new aspell (0.50-20020815 in portage in a few minutes) and merge an aspell dictionary (I'm gradually adding more and more) then, remerge gnome-spell then try evolution :) then report back here :)
I followed your steps and you may know this already, but emerging gnome-spell requires pspell, ispell, and pspell-ispell as dependencies, so basically I'm just re-compiling gnome-spell against the new aspell. Just so its clear as to what exactly I'm doing (I don't know if I was supposed to hack gnome-spell to not require ispell/pspell). Anyway, I tried using --nodeps to avoid merging ispell/pspell, and gnome-spell refused to compile. So, with gnome-spell emerged in the presence of aspell, ispell, pspell, and pspell-ispell, spell checking works, but its using ispell. My language setting in gnome's html view properties is "en". I tried changing it to aspell-en as previously suggested, and I get: ORBit-WARNING **: Request notify, ID -1073745596 was rejected by the authentication mechanism! ORBit-WARNING **: Request notify, ID -1073745596 was rejected by the authentication mechanism! Note that I'm running everything (gnome, gnomecc, etc.) as the same normal user. I imagine that the language change may not be actually being made b/c of the errors? I don't know enough about ORBit. Is there a way to set it manually, or to get rid of that error? Sorry for being clueless about ORBit & gconf & friends.
ouch, my fault. OK, I have put a new ebuild into portage for gnome-spell, and masked it. OK, so the procedure will be to unmerge pspell, ispell, pspell-ispell and aspell, and then merge the new aspell (0.50.20020815) as well as some dictionaries for it (which are masked as well, I think). I will be adding more and more dictionaries for the new aspell over the weekend. You want the 0.1.0.10 type versions for the dictionaries (ie, version wise, NOT the latest according to portage). Lemme know :)
OK, I did emerge aspell aspell-en gnome-spell (aspell-en's depend on aspell is broken for me btw, says it can't find =app-text/aspell-0.50*, but the newer of the two aspell-0.50*'s is already emerged...). Apart from the dep problem, it seems to work great, and gnome-spell is definitely using aspell for its spell-checking when ispell and pspell aren't present. I also tried emerging gnome-spell while ispell, pspell, pspell-ispell, and aspell were installed, and it used ispell. I would have tried changing between aspell and ispell but I don't know how to get rid of the error I mentioned before. It is good that evolution now works with whatever is installed. I really don't have much of a preference for one of the 3 (aspell, ispell, pspell) or the other, but some things require one, some require others, and it seemed that most used ispell/pspell. Is there any easy way to get them to share a single personal dictionary (it seems ispell and pspell do this, but aspell has a slightly different format), or to use one spell-checker for all apps? (I realize this may not be a gentoo problem, but a big mess in general, just looking for any suggestions since I don't know how the 3 interact w/ programs)
I've been trying to emerge evolution but I keep getting a broken pipe during the install. I'm building using the the defaults in make.conf for the p3 and higher (only) procs. perhaps the 0.33.7.1-r2 should be unmasked The error follows Making all in data make[2]: Entering directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' cd ../; bd=`pwd`; cd scowl/final; \ cat english-*.10 english-*.20 english-*.35 english-*.50 \ english-*.60 english-*.65 \ special-*.35 special-*.50 \ | $bd/src/aspell --lang=english \ create master $bd/data/english-med-only cd ../; bd=`pwd`; cd scowl/final; \ cat american-*.10 american-*.20 american-*.35 american-*.50 \ american-*.60 american-*.65 \ | $bd/src/aspell --lang=english \ create master $bd/data/american-med-only cat: write error: Broken pipe make[2]: *** [american-med-only] Error 134 make[2]: *** Waiting for unfinished jobs.... cat: write error: Broken pipe make[2]: *** [english-med-only] Error 134 make[2]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3587, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/app-text/aspell/aspell-0.33.7.1-r1.ebuild .
adam, comment out the line in /usr/portage/profiles/package.mask for aspell, and then emerge aspell, then gnome-spell, and you'll be all set. As for you Justin, there are only a very few apps which use plain ispell (and aspell serves as a suitable replacement). There are some which use pspell-ispell. And others which use only aspell. Pspell in the current unmasked form is only a wrapper around aspell and ispell. However, the new aspell (masked version) is, in fact, a combination of pspell and aspell. What this all means is that in the very near future, we can probably switch _everything_ to just plain old aspell :)
new aspell unmasked and new gnome-spell unmasked which uses it.
