On 18/05/17 02:33, James McCoy wrote:
Control: reassign -1 gpm 1.20.4-6.2
Control: merge 775443 -1
On Wed, May 17, 2017 at 05:12:55PM +0000, Alan Jenkins wrote:
This happens when running `vi` inside a systemd-nspawn container.
`vi` is able to run, but each time it logs three lines in
attention-getting RED (loglevel alert) in the system log.
strace shows that vi looks for /dev/vc/0 and /dev/tty0.
Neither of these exist in /dev, this is expected in a container.
This is triggered by some debian-enabled configuration.
Actually, it's triggered by the lack of a user configuration, so Vim
loads defaults.vim, which does "set mouse=a". Since you're in a
console, that's handled by gpm.
May 17 16:55:36 unstable vim[761]: unable to open gpm console, check your /dev
filesystem!
May 17 16:55:36 unstable vim[761]: *** err
May 17 16:55:36 unstable vim[761]: Oh, oh, it's an error! possibly I die!
Which are all emitted by gpm[0]. It looks like this has already been
reported[1] against gpm ... over 2 years ago.
[0]: https://codesearch.debian.net/search?q=Oh%2C+oh%2C+it%27s+an+error
[1]: https://bugs.debian.org/775443
Cheers,
Thanks for that. I just saw /etc/vim/vimrc referring to default.vim, I
overlooked that default.vim was from upstream.
I'm not sure what you mean by a console. The tty is `/dev/pts/0` (the
other end is `machinectl login` on the host system).
#775443 says it goes away when removing gpm, so it's not exactly the
same. I had never installed gpm on my nspawn container. vi does pull
in libgpm though.
The specific error I saw comes from here:
https://github.com/telmich/gpm/blob/1.20.4/src/lib/liblow.c#L213
"what's with the lib??? ... making this piece of code work has been a
real hassle ..."
Regards
Alan
