Re: Lyx 2.5.0 crash on mac book pro arm cpu

Scott Kostyshak via lyx-users <[email protected]> Tue, 17 Mar 2026 08:28:38 +0100

Newsgroups	gmane.editors.lyx.general
Message-ID	<abkBb2Be1ZUJh7ES@jimmy>

On Mon, Mar 16, 2026 at 04:35:53PM -0700, Chris Menzel wrote:
> >
> > Similar experience here with LyX 2.5.0 on an M4 Mac mini running 26.3.1.
> >> However, it only happens if I quit (via LyX → Quit LyX) with a LyX window
> >> open, whether or not a file is loaded. If I first close any open LyX
> >> windows and then quit via LyX → Quit LyX, I do not get the crash report
> >> window. Other than this, no issues with 2.5.0.
> >
> >
> > Ah this is very intersting! Perhaps this is already known, but if not,
> > your observation gives an idea for a quick workaround (and for narrowing
> > in on the root cause).
> >
> > Chris, Can you open some documents and then open the command buffer (I
> > think with alt+x or command + x maybe on mac?). This will open a small
> > toolbar at the bottom of your screen. Enter the following in the toolbar
> > and press Enter:
> >
> >   command-sequence buffer-close-all; lyx-quit
> >
> > Does it quit successfully, without crash, if you do it this way?
> 
> 
> The first time I tried it, it only closed the open buffer on my document. I
> then quit manually but indeed I did not get the crash window. However, now
> when I try to enter the command in the command buffer, I get a "command
> disabled" message. ¯\_(ツ)_/¯

Thanks for trying! Well dang, I expected that to work. If anyone else
can try that command-sequence on macOS, that would be helpful. I still
think it could be a nice workaround to the bug (if it works, we can
change the menu to run that command). But if the command-sequence
doesn't work on its own, that good be a different (or related?) bug.

Scott

-- 
lyx-users mailing list
[email protected]
https://lists.lyx.org/mailman/listinfo/lyx-users

signature.asc (application/pgp-signature, 488 B)