Package: neovim Version: 0.3.4-2 Severity: important I just wanted to see how nvim behaves but ...
$ nvim Segmentation fault (core dumped) $ nvim -u NONE Segmentation fault (core dumped) $ nvim -u NORC Segmentation fault (core dumped) $ dpkg -l neovim Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= ii neovim 0.3.4-1 amd64 heavily refactored vim fork Then I did: $ sudo apt-get install -t unstable neovim 0.3.4-2 installed but I get the same "Segmentation fault (core dumped)" Since I am using -u option, this can't be vim interference... Please at least add README.Debian if there is some limitation for use environment. I didn't investigate much ... it's strange since this should be at least working at James' terminal ... -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages neovim depends on: ii libc6 2.28-10 ii libluajit-5.1-2 2.1.0~beta3+dfsg-5.1 ii libmsgpackc2 3.0.1-3 ii libtermkey1 0.20-3 ii libunibilium4 2.0.0-4 ii libuv1 1.24.1-1 ii libvterm0 0~bzr718-1 ii neovim-runtime 0.3.4-2 Versions of packages neovim recommends: ii python-neovim 0.3.0-1 ii python3-neovim 0.3.0-1 ii xclip 0.13-1 ii xsel 1.2.0+git9bfc13d.20180109-1 ii xxd 2:8.1.0875-3 Versions of packages neovim suggests: ii exuberant-ctags [ctags] 1:5.9~svn20110310-12 ii vim-scripts 20180807 -- no debconf information
