[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-06-17 Thread Mike Dotson
Installing vim package resolves the issue of `vi empty`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872896 Title: terminfo file xterm-256color has entries that make vi unusable when sshing in

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-06-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ncurses (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872896 Title:

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-19 Thread Guntram Blohm
** Package changed: ubuntu => ncurses (Ubuntu) ** Changed in: ncurses (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872896 Title: terminfo file

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Guntram Blohm
I made a small video where I'm calling vi in different ways. Every time, I press a for insert mode, type a few characters, then press ESC to exit insert mode again. ** Attachment added: "Running vi/vim to show the problem"

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Guntram Blohm
I checked which vi I'm using - it's /usr/bin/vi, which links to /etc/alternatives/vi, which links to /usr/bin/vim.tiny. Then, to make sure, I created an empty file (touch empty) and used the full path of to run vi on that file, with and without -u NONE. /usr/bin/vi empty - the sequence ?>4;m

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Brian Murray
I was unable to recreate this. Have you tried not loading any vimrc files to see if that changes the behavior? ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Guntram Blohm
It seems like the package is ncurses-base, which provides /lib/terminfo/x/xterm-256color, but as /lib is a symlink to /usr/lib, the file ends up there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Guntram Blohm
I ran apport-collect on the focal, but got the message "no additional information collected" every time. Hope some info got through anyway. I would have loved to state the package name, but the only thing I know is the filename - /usr/lib/terminfo/x/xterm-256color. Neither apt-file search

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1872896 When reporting bugs in the future please use apport by using 'ubuntu-

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-04-15 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people