Summary: | VIM 6.1 Borked. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ryan Wehler <mindflux_98> |
Component: | New packages | Assignee: | Seemant Kulleen (RETIRED) <seemant> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | esigra, goluptious, jvm, underactive |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ryan Wehler
2002-04-02 01:11:54 UTC
emerge the latest portage (1.8.10) and try this again. I have been unable to duplicate it at all on my system, and the oneother person who reported the problem can not duplicate it either. VIM works just fine via a SSH install, so if you aren't at the actual computer using one of the tty's it works just fine.. stinky! i'm getting the same ACCESS VIOLATION message on a fresh Gentoo install + emerge KDE. updated to portage 1.8.11 and emerged VIM again but got the same error. Install of Gentoo 1.0 (stage 3 type install) yesterday and emerged gnome (and all that implies). Was ready to get back to using X when I emerged vim and hit this bug (just as initial bug reporter listed it, AFAICT). Version of portage is 1.8.9. Used ebuild as follows: emerge vim [dies as per this bug] ebuild vim-6.1.ebuild install [installs, this step had been done by emerge before it died] ebuild vim-6.1.ebuild package [to save all the work into a package] emerge --usepkg vim [install using binary package we just built] That worked. Since the order of steps I just outlined should at least be *close* to what emerge vim would do by itself, it seems like a real bug to me. But I have no idea why. I ran into this problem a few days ago and thought that the ebuild was telling me that I had the wrong permissions on /dev/vc/1, so I changed the permissions and retried the ebuild. It installed without a problem. ok wait -- what did you change the permissions to? I had created a -r1 ebuild which predicted a write in the sandbox. It felt wrong, and now I am closer to knowing why. Can all of you who had this problem upgrade your following files please: /etc/pam.d/xdm /etc/pam.d/gdm /etc/pam.d/gdmconfig And if anyone is not using xdm or gdm (or kdm) as a login manager (ie if you are startx'ing) please inform me immediately, we need to talk! Sean Bob, Read this bug report, I need info! Sorry Seemant, I tried connecting to this site for about 6 hours last night (I live in Taiwan, GMT+8) but I was unable to get through to anything @ gentoo.org. Anyways, I added read and write permissions for group and others: chmod 666 /dev/vc/1 but this reverted back to 600 after I logged out and back in again. Although, VIM is still working fine. As for login managers, I don't use an X-based login manager; I only use startx when I need X. Sean Bobb Sean Bob, Thanks for the info. Actually, you were quite quick to respond. gentoo.org was in fact down for about 6 hours last night, so you're ok :) *** This bug has been marked as a duplicate of 1531 *** I beleive I have found the (real) solution! Simply add root (or whoever you have emerging things) to the 'tty' group. Just change line 6 (on my mostly new system) of /etc/group to: tty::5:root |