You are not logged in.
After upgrading to the latest neovim version 0.2.2-2 (unibilium rebuild, no other changes to the neovim source). Neovim has been crashing my tmux session and messing up the terminal escape characters in st term.
Weirdly other terminals, such as xfce-terminal are not affected.
Disabling configuration for neovim does not help. Normal Vim 8.0 is unaffected.
Unfortunately I was not able to downgrade neovim because of library loading issues.
I suspect the issue to lie in some faulty terminfo issues, but any help debugging this is issue is appreciated.
Offline
I can reproduce the failure. Here's a less-than-helpful tmux stack trace at the point of the crash:
(gdb) where
#0 0x00007fae8d1fff11 in __strlen_avx2 () from /usr/lib/libc.so.6
#1 0x00007fae8d90ea98 in tparm () from /usr/lib/libtinfo.so.6
#2 0x0000564e276fc7d7 in ?? ()
#3 0x0000564e276fd9e1 in ?? ()
#4 0x0000564e276fe93b in ?? ()
#5 0x0000564e276f220e in ?? ()
#6 0x0000564e276f3c7e in ?? ()
#7 0x0000564e276e9a12 in ?? ()
#8 0x0000564e276f4285 in ?? ()
#9 0x0000564e276c0b99 in ?? ()
#10 0x0000564e276bd312 in ?? ()
#11 0x00007fae8d0c9f4a in __libc_start_main () from /usr/lib/libc.so.6
#12 0x0000564e276bd4ea in ?? ()I hope to chase this a little more later but that's all I've got for now.
Offline
I have tried fixing this error by rolling back packages and have traced the causing package to be ncurses 6.1. Rolling back to ncurses 6.0 actually fixes the issue.
EDIT: The weird issue is that I had another setup with working neovim + tmux with ncurses 6.1 which worked before upgrading unibilium to 2.0, but stopped working after upgrading. But downgrading ncurses to 6.0 also resolves the issue, whereas downgrading unibilium doesnt actually help.
Last edited by Alcasa (2018-02-24 14:01:03)
Offline
Same here, anther application affected is alot ( https://aur.archlinux.org/packages/alot/ ).
Might be related to this bug: https://bugs.archlinux.org/task/57300
//edit: Actually, I'm not 100% sure the issue with alot is the same. Maybe, maybe not. In any case, the problem with neovim exists and is solved once downgrading ncurses.
Last edited by lamarpavel (2018-02-25 18:00:39)
Offline
I'm having this exact same problem, but downgrading to ncurses 6.0 doesn't seem to help. What does help, however, is changing TERM from screen-256color to just screen.
Offline
Yes, I also get the same issue but vim seems to work fine.
Offline
I was having the same issue. Downgrading ncurses to 6.0 fixed it for me.
Offline
There is a bug report for this:
https://bugs.archlinux.org/task/57596
This should be fixed with an update to ncurses 20180224 or newer, the current ncurses version in the repository is from 20180129. Until then, the workaround described in the bugreport fixes the issue.
Offline