touch-packages team mailing list archive

[Bruce Pieterse <dev@xxxxxxxxxx>]

In my case I accidentally used sudo vi /etc/ instead of the full path of the file
sudo vi /etc/asterisk/manager.conf. Vim opened normally, I just exited
straight away with :q, but the crash report only occurred a few hours
later.

History confirms timestamp:
41328* 2015-01-13 14:21  sudo vi /etc/

Vim crashed at roughly 17:01.

Original bug report #1410294.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/957793

Title:
  vim.basic crashed with SIGSEGV

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  it crashed when i run " vim –version |grep -o ‘+clientserver\|+signs’
  "

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: vim 2:7.3.429-2ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Sat Mar 17 18:01:45 2012
  ExecutablePath: /usr/bin/vim.basic
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20120313)
  ProcCmdline: vim –version
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: vim.basic crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/957793/+subscriptions