Attempting to emerge xine-lib-1.0, it unpacks and configures, and apparently directly after the configure it starts spitting out sandbox violations. The violation log is 30K+ lines long, including /dev/urandom reads, /tmp/* writes (note that I have PORTAGE_TMPDIR="/tmp"), and even what appears to be standard execution calls, etc. It's as if the sandbox was reset to null, so EVERY file system access is a violation. Sandbox violation log and emerge log will be attached. Is this safe to disable sandbox on? Reproducible: Always Steps to Reproduce: 1. Attempt to emerge xine-lib-1.0 Actual Results: See Details. 30K+ lines of sandbox violations, failed emerge. Expected Results: Successful emerge Portage 2.0.51-r8 (default-linux/amd64/2004.3/lib64, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-rc3 x86_64) ================================================================= System uname: 2.6.10-rc3 x86_64 AMD Opteron(tm) Processor 242 Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jul 26 2004, 01:21:27)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -Os -pipe -funit-at-a-time -fomit-frame-pointer -frename-registers -fweb -fPIC" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /m /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config/usr/lib/X11/xkb /usr/share/config /usr/share/mc /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -Os -pipe -funit-at-a-time -fomit-frame-pointer -frename-registers -fweb -fPIC" DISTDIR="/p/src" FEATURES="autoaddcvs autoconfig buildpkg candy ccache confcache distlocks sandbox" GENTOO_MIRRORS="ftp://gentoo.ccccom.com http://gentoo.osuosl.org/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://mirror.datapipe.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo" MAKEOPTS="-j3" PKGDIR="/p/pkg" PORTAGE_TMPDIR="/tmp" PORTDIR="/p" PORTDIR_OVERLAY="/usr/local/p" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="amd64 X aac acpi alsa apm arts audiofile avi berkdb bitmap-fonts caps cdparanoia cdr crypt cups curl dga divx4linux dvd dvdr encodefam flac font-server foomaticdb gdbm gif gpm gstreamer gtk gtk2 imlib ithreads jp2 jpeg kde libwww lzw lzw-tiff mad maildir micmod mng motif mozilla mpeg multilib ncurses no-old-linux nptl nptlonly offensive oggvorbis opengl oss pam pdflib perl pic png ppds python qt quicktime radeon readline scanner slang speex spell ssl tcltk theora tiff truetype truetype-fonts type1-fonts usb userlocales xine xinerama xml2 xosd xpm xrandr xv xvid zlib video_cards_ati input_devices_keyboard input_devices_mouse linguas_en"
Created attachment 46945 [details] sandbox violation log
Created attachment 46947 [details] portage emerge log This is sans sandbox violation log previously submitted.
FWIW... When I use FEATURES=userpriv instead of sandbox, I get the HAVE_XV error described in 75764, but I expect this bug is unrelated to that.
It appears to work fine, now, after the changes of the last few days. No more sandbox violations, and the HAVE_XV error gone as well. Just merged the update, then tried running it, with no problems at all. Setting resolution FIXED.
