Summary: | ACCESS VIOLATION while compiling kile-1.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Georgios E. Kylafas <gekylafas> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Georgios E. Kylafas
2003-03-18 20:05:42 UTC
Are you running portage as root, as user, sudoing as root, suing to root, or what? I am running it as root from konsole. In my konsole settings, the "Root Console" session is initiated by executing "su -". Although my previous comment says that I am running root executing "su -", it seems that this was not the case eventually. I opened up a new konsole session with "su -", and kile emerged succesfully. I should note, though, that the session that gave me problems with kile has been used numerous times for emerging packages, without any access violation problems. Oh, well... So you can't reproduce this anymore? If so, please close the bugreport (since I couldn't reproduce it to begin with). I suppose I could reprodyce it if I tried. Perhaps by doing a plain "su" before emerging, thus leaving $USER to be a user other than root. Anyway, this was not really a bug with the ebuild, so I am resolving it to INVALID |