Re: Diagnosing a crash
On 03/13/2018 11:30 AM, Jean-Marc Lasgouttes wrote: Le 13/03/2018 à 16:26, Paul A. Rubin a écrit : Aspell is only available if the development headers (e.g. libaspell-dev on debian) are available at compile time . JMarc Ah. I installed the precompiled package from Liv's PPA, so I guess he compiled it without Aspell (which is fine with me). When you do "lyx -version" the special build flags line will contain entries like use-enchant, use-hunspell, that tell you what spell checkers have been selected. Not that enchant is a wrapper library that relies on other spellcheckers that can be aspell, hunspell, etc. JMarc JMarc Looking at the enchant ordering file (and what is installed on my system), it appears that enchant is using aspell. So the crash with 2.2.3 occurred when aspell was invoked directly but not when it was invoked through enchant. Curiouser and curiouser. Paul
Re: Diagnosing a crash
Le 13/03/2018 à 16:26, Paul A. Rubin a écrit : Aspell is only available if the development headers (e.g. libaspell-dev on debian) are available at compile time . JMarc Ah. I installed the precompiled package from Liv's PPA, so I guess he compiled it without Aspell (which is fine with me). When you do "lyx -version" the special build flags line will contain entries like use-enchant, use-hunspell, that tell you what spell checkers have been selected. Not that enchant is a wrapper library that relies on other spellcheckers that can be aspell, hunspell, etc. JMarc JMarc
Re: Diagnosing a crash
On 03/13/2018 11:12 AM, Jean-Marc Lasgouttes wrote: Le 13/03/2018 à 15:56, Paul A. Rubin a écrit : Apparently not. I just upgraded to 2.3.0. It selected Enchant as the spellchecker and did not give me any options in the drop-down list (even though aspell is installed here). On the bright side, that eliminates the bug. Aspell is only available if the development headers (e.g. libaspell-dev on debian) are available at compile time . JMarc Ah. I installed the precompiled package from Liv's PPA, so I guess he compiled it without Aspell (which is fine with me). Paul
Re: Diagnosing a crash
Le 13/03/2018 à 15:56, Paul A. Rubin a écrit : Apparently not. I just upgraded to 2.3.0. It selected Enchant as the spellchecker and did not give me any options in the drop-down list (even though aspell is installed here). On the bright side, that eliminates the bug. Aspell is only available if the development headers (e.g. libaspell-dev on debian) are available at compile time . JMarc
Re: Diagnosing a crash
On 03/13/2018 04:37 AM, Pavel Sanda wrote: Paul A. Rubin wrote: .cset" could not be opened for reading or does not exist.lib/aspell/ Aborted (core dumped) This looks totally weird. The correct error should say something like "lib/aspell/your_encoding.cset" could not be opened for reading or does not exist. Maybe the encoding is set to some strange character? Is the same problem with 2.3.0? Actually do we even support aspell with 2.3.0? Pavel Apparently not. I just upgraded to 2.3.0. It selected Enchant as the spellchecker and did not give me any options in the drop-down list (even though aspell is installed here). On the bright side, that eliminates the bug. Paul
Re: Diagnosing a crash
Paul A. Rubin wrote: > >.cset" could not be opened for reading or does not exist.lib/aspell/ > >Aborted (core dumped) This looks totally weird. The correct error should say something like "lib/aspell/your_encoding.cset" could not be opened for reading or does not exist. Maybe the encoding is set to some strange character? Is the same problem with 2.3.0? Actually do we even support aspell with 2.3.0? Pavel
Re: Diagnosing a crash
On 03/12/2018 07:41 PM, Richard Heck wrote: On 03/12/2018 07:36 PM, Paul A. Rubin wrote: Hi all, I have a very perplexing but utterly repeatable crash that I'm trying to diagnose, to determine whether I should file a ticket (or whether it's not a LyX issue). I'd appreciate any insight. Apologies for the length of what follows. Any time LyX crashes, it is a problem. The error may be coming from elsewhere, but we should deal with it. So I'd suggest filing a ticket. Richard Will do (tomorrow -- dinner beckons now). Paul
Re: Diagnosing a crash
On 03/12/2018 07:36 PM, Paul A. Rubin wrote: > Hi all, > > I have a very perplexing but utterly repeatable crash that I'm trying > to diagnose, to determine whether I should file a ticket (or whether > it's not a LyX issue). I'd appreciate any insight. Apologies for the > length of what follows. Any time LyX crashes, it is a problem. The error may be coming from elsewhere, but we should deal with it. So I'd suggest filing a ticket. Richard
