emerge ACCESS VIOLATION

BeesTea · n00b Joined: 17 May 2003 Posts: 4

Greetings,

I've recently added ~x86 as a KEYWORD. Upon my first emerge -u world following the change I get the following.

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-xscreensaver-4.09-4853.log"

open_wr: /var/lib/rpm/__db.Name.
--------------------------------------------------------------------------------

Interestingly, I am not using the sandbox feature. Rpm is installed because I use ICC when I can.

Here is what I've tried.

etc-update # To add the changed files from the software changes that did work prior to this error.

env-update
source /etc/profile

emerge regen # This was listed in anoher thread as a work around for a similar problem.

If anyone has any insight on this it would be much apreciated.

Cheers,
-BeesT

IonK · n00b Joined: 14 May 2003 Posts: 3 Location: Berlin

same problem too while updating my gentoo :cry:

-> emerge rsync
-> emerge -u world

make[1]: Leaving directory `/var/tmp/portage/xscreensaver-4.09/work/xscreensaver-4.09/hacks/glx'
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-xscreensaver-4.09-3406.log"

open_wr: /var/lib/rpm/__db.Name.
--------------------------------------------------------------------------------

i stay tuned for some help!
_________________
--------------------------------------------------------------------------------
Have Problem with Windows !? > reboot
Have Problem with Linux !? > be root

dippen · Tux's lil' helper Joined: 15 Sep 2002 Posts: 83

Woland · Posted: Wed May 28, 2003 8:05 am Post subject:

Just had the exact same problem while emerging gphoto2. Never seen the like error before.

The export SANDBOX_DISABLED=1 did the trick, but left me puzzled. Should this bu Bugzilla'd?

bludger · Guru Joined: 09 Apr 2003 Posts: 389

I also had the same problem emerging gocr.