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

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).


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

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, 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

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 if the development headers (e.g. libaspell-dev 
on debian) are available at compile time .


JMarc


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

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

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. 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

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.

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



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 Qt version is 4.8.7 
(both compile-time and run-time). I have Aspell, Enchant and Myspell 
installed. The OS uses English (US) as its default language.


Symptom #1: With Aspell selected as the spellchecker, if I attempt to 
spellcheck any document, no matter how simple, LyX crashes. The crash 
message is

.cset" could not be opened for reading or does not exist.lib/aspell/
Aborted (core dumped)

With Enchant selected, there is no problem.

Symptom #2: With Aspell set as the spellchecker, if I right click in any 
empty document, or on the handle of a float, things work as expected. If 
I right click in the text area of a non-empty document, I get the same 
crash. Here's the tail of output when I ran LyX with dbg -any and 
triggered the crash:

frontends/qt4/Menus.cpp (2342): Context menu requested: context-edit
frontends/qt4/Menus.cpp (2297): Triggered menu: context-edit
AspellChecker.cpp (214): aspell user dir: /home/paul/.lyx/
AspellChecker.cpp (217): aspell sysdir dir: /usr/share/lyx/
.cset" could not be opened for reading or does not exist.lib/aspell/
Aborted (core dumped)
So the right-click triggered a context menu, which then somehow seems to 
have invoked Aspell (?!) and caused the crash.


Just to make this dopier, I have the same operating system and same 
version of LyX installed on my laptop and an older PC with no problems. 
The crash is happening on a new machine (with a different chip 
architecture, which hopefully does not matter) that I'm breaking in.


Any suggestions on (a) why a right-click in the middle of some text 
would have anything to do with the spellchecker and (b) why Aspell is 
blowing up on just this one machine?


Thanks,
Paul