Re: Diagnosing a crash

2018-03-13 Thread Paul A. Rubin
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 com

Re: Diagnosing a crash

2018-03-13 Thread Jean-Marc Lasgouttes
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). Wh

Re: Diagnosing a crash

2018-03-13 Thread Paul A. Rubin
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,

Re: Diagnosing a crash

2018-03-13 Thread Jean-Marc Lasgouttes
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

Re: Diagnosing a crash

2018-03-13 Thread Paul A. Rubin
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 doe

Re: Diagnosing a crash

2018-03-13 Thread Pavel Sanda
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

Re: Diagnosing a crash

2018-03-12 Thread Paul A. Rubin
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. Apologie

Re: Diagnosing a crash

2018-03-12 Thread Richard Heck
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. A

Diagnosing a crash

2018-03-12 Thread Paul A. Rubin
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. I'm running LyX 2.2.3 on Linux Mint 18.3 MATE. The Q