Le Thu, Apr 25, 2024 at 05:00:26PM +0200, Frederic Cambus a écrit :
> On Wed, Apr 24, 2024 at 08:21:38AM +0200, Landry Breuil wrote:
> 
> > > I previously didn't notice this, it always ran fine here during my tests:
> > > launching it in tmux worked both locally and through SSH.
> > > 
> > > But launching it in alacritty outside of tmux indeed results in a crash,
> > > although it works fine in xterm or in a framebuffer console.
> > 
> > interestingly, it started working once i had rm -Rf ~/.lnav. so i guess
> > something something corrupted internal database ?
> > 
> > does it work again if you move away ~/.lnav on the machine where it
> > crashes ?
> 
> On my machine it creates ~/.config/lnav, not ~/.lnav, and removing the
> ~/.config/lnav directory unfortunately doesn't change anything, it still
> crashes early at startup.

it probably does funky things depending on $TERM.

it works fine within tmux where TERM=screen, it crashes in
xfce4-terminal (where here TERM=xterm-256color) but works fine if i
manually set TERM=xterm.

same thing with alacritty, it crashes if TERM=alacritty (the default)
but works fine with 'TERM=xterm lnav'

you seem to be a guy with interest in low-level terminal stuff :) grep
-r TERM yields many things in lnav's code... and there seem to be
related issues upstream, cf https://github.com/tstack/lnav/issues/570
and https://github.com/tstack/lnav/issues/1192 at least. But it shouldnt
crash like this :)

in the meantime, here's a port of 0.12.2, still building here... it
might give better results, or not.

https://github.com/tstack/lnav/releases/tag/v0.12.2

Landry

• lnav-0.12.2.tgz (3K)