VIM hangs and pegs CPU as non-root

[chardros]

Subject says it all... if I run vim as any user other than root, it just hangs and pegs my CPU at 99.9%. If I run as root, it works perfectly. Anyone run into anything similar to this? (It occurs both in an X/E/Gnome Terminal within X, and at the console... GVIM works fine as any user).

Info -
vim-6.1-r10 is installed (with gtk, x bindings, etc)
kvim-6.1.141_rc1 is installed (also works fine as any user)
ls -l /usr/bin/vim returns:
-rwxr-xr-x 1 root root 1141176 Aug 23 10:27 /usr/bin/vim

Thanks in advance for any advice.

[Naan Yaar]

You can probably try "strace vim" to see what it is doing.

[chardros]

strace vim ends with this:
...
<snip>
open("/usr/X11R6/lib/X11/locale/locale.dir", O_RDONLY) = 5
fstat64(5, {st_mode=S_IFREG|0444, st_size=27992, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
x40b38000
read(5, "#\t$Xorg: locale.dir,v 1.3 2000/0"..., 4096) = 4096
read(5, "CALE\t\t\tfr_BE.ISO8859-15\niso8859-"..., 4096) = 4096
read(5, "CVN\nvi_VN.viscii/XLC_LOCALE\t\tvi_"..., 4096) = 4096
read(5, "v_LV.UTF-8\nen_US.UTF-8/XLC_LOCAL"..., 4096) = 4096
close(5) = 0
munmap(0x40b38000, 4096) = 0
open("/usr/X11R6/lib/X11/locale/C/XI18N_OBJS", O_RDONLY) = 5
fstat64(5, {st_mode=S_IFREG|0444, st_size=333, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
x40b38000
read(5, "# CATEGORY(XLC|XIM|OM)\tSHARED_LI"..., 4096) = 333
read(5, "", 4096) = 0
close(5) = 0
munmap(0x40b38000, 4096) = 0
open("/usr/X11R6/lib/X11/locale/common/xlcDef.so.2", O_RDONLY) = 5
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000\10\0"..., 1024) = 10
24
fstat64(5, {st_mode=S_IFREG|0644, st_size=12196, ...}) = 0
old_mmap(NULL, 12200, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0) = 0x40b38000
mprotect(0x40b3a000, 4008, PROT_NONE) = 0
old_mmap(0x40b3a000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 5, 0x100
0) = 0x40b3a000
close(5) = 0
brk(0x81cb000) = 0x81cb000
brk(0x81cc000) = 0x81cc000
open("/usr/X11R6/lib/X11/locale/locale.alias", O_RDONLY) = 5
fstat64(5, {st_mode=S_IFREG|0444, st_size=48229, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
x40b3b000
--- SIGSEGV (Segmentation fault) --- --- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation
fault) ---
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation fault) -
--
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation fault) ---
--- SI
GSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (S
egmentation fault) ---
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentat
ion fault) ---
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation faul
t) ---
--- SIGSEGV (Segmentation fault) ---
--- SIGSEGV (Segmentation fault) ---
--
- SIGSEGV (Segmentation fault) ---

...

And it keeps going and going and going like that until I kill it.

Again.. it runs fine as root. I'm at a loss.

[rac]

To try to isolate likely permission errors, could you try running strace with something like:

[chardros]

Thanks for the thoughts guys... turns out it was my own dumb fault. I had emerged the masked kvim... and the package.mask file stated that it conflicted with "plain vim". So I unmerged kvim, re-emerged vim and I'm golden. Thanks again for the help.

[Scott_the_Great]

Luckily I didn't run into this problem, because I happened (just chance, I can assure you) to read the changelog before trying to install kvim.
However, since I *really* wanted to try it out, I spent a little time today hacking the ebuild so that it would no longer conflict with the "regular" vim. (Instead, it depends on it...)

I also changed it so that it would get kvim-6.1-rc2 instead of rc1 (which was the most recent ebuild I had...)

I just put the following ebuild (kvim-6.1.141_rc2.ebuild) in my local portage directory (specified with PORTDIR_OVERLAY in /etc/make.conf) and everything worked like a charm. It spit out a couple of strange errors, but the install directory (/var/tmp/portage/kvim-6.1.141_rc2/image) looked OK, and it merged without problem.

Basically, in the ebuild, I just manually remove all of the "conflicting" stuff from the temp install directory before the merge happens. If you want to be safe about this, I would recommend trying to do an "ebuild ... install" and then check the temp install directory to make sure it isn't going to replace any files you already have in /usr/bin... (then you must do an "ebuild ... qmerge" to actually perform the emerge...)

Also, because of the way this works, all of the vims will use the same set of help files and vimrc file (which is good, I think...)

Let me know if anyone has any problems with this, or any suggestions to make it work better.

---Scott