Is this still an issue for you? Which Ubuntu version do you use? Thank
you for telling us!
** Changed in: vim (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thomas Hotz wrote:
Is this still an issue for you?
As I wrote earlier, this issue has been fixed upstream on Oct 30 2007 in
this version of Vim:
7.1.147 (after 7.1.127) freeing memory twice completing user name
That's about about 5 years ago now.
I don't think any supported version of Ubuntu
Thank you for clarification!
** Changed in: vim (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195264
Title:
vim.gnome crashed with SIGSEGV in
Can not reproduce on Ubuntu Natty. Does it still applies?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195264
Title:
vim.gnome crashed with SIGSEGV in free()
To manage notifications about this
I get the same bug in Maveric Ubuntu. I removed vim-gnome and installed
vim-gtk and the bug went away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195264
Title:
vim.gnome crashed with SIGSEGV in
Ignore my comment above. It also couses crashes. I anyhow only use the
vim command in a shell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195264
Title:
vim.gnome crashed with SIGSEGV in free()
Please don't change the status without explaining why you're doing so.
Especially since Opinion counts as closing the bug, see
https://wiki.ubuntu.com/Bugs/Status
** Changed in: vim (Ubuntu)
Status: Opinion = New
--
vim.gnome crashed with SIGSEGV in free()
** Changed in: vim (Ubuntu)
Status: New = Opinion
--
vim.gnome crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/195264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
Binary package hint: vim
On current Hardy, vim crashes.
How to reproduce:
1.) start the text-based vim in a terminal window
2.) enter random text
3.) press v to enter visual mode
= crash
ProblemType: Crash
Architecture: i386
Date:
** Description changed:
Binary package hint: vim
On current Hardy, vim crashes.
How to reproduce:
1.) start the text-based vim in a terminal window
2.) enter random text
3.) press v to enter visual mode
= crash
ProblemType: Crash
Architecture: i386
Date:
Vim-7.1.138 in Ubuntu-8.04 has a known severe bug which causes it to
segfault (double free). It happens at least when doing completion on
user names.
It's fixed upstream on Oct 30 2007 (more than 1 year ago) in this patch:
7.1.147 (after 7.1.127) freeing memory twice completing user name
I
Something changed: setting TERM to linux did not helped anymore.
But changing locale settings in /etc/environment/ from hu_HU.utf8 (that
is listed in locale -a) to hu_HU.UTF-8 resolved the problem.
--
vim.gnome crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/195264
You received
bug still exists
Setting TERM=linux avoids the crash.
Could someone please point out why this happens?
** Visibility changed to: Public
--
vim.gnome crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/195264
You received this bug notification because you are a member of Ubuntu
13 matches
Mail list logo
