If the root user doesn't have a .gconfd directory in his home dir, gnome-extra/gnome-utils-2.2.1.ebuild generates a sandbox violation trying to create it. Reproducible: Always Steps to Reproduce: 1. mv /root/.gconfd /root/old.gconfd 2. ebuild /usr/portage/gnome-extra/gnome-utils/gnome-utils-2.2.1.ebuild merge Actual Results: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-gnome-utils-2.2.1-24997.log" mkdir: /root/.gconfd mkdir: /root/.gconfd mkdir: /root/.gconfd -------------------------------------------------------------------------------- Expected Results: A successful merge. A workaround appears to be creating a .gconf dir for the root user manually: mkdir /root/.gconfd
probably a dup you don't give your 'emerge info' :( *** This bug has been marked as a duplicate of 17380 ***
the following attachments are an updated ebuild, and a patch against the offending Makefile.in's in the source. there does exist a configure option to --disable-schema-install, which you'd hope would fix the problems as in bug 17380, however unlike in that bug --disable-schema-install isnt implemented properly (or at all) in the Makefile.in's for gnome-utils which is why the patch is required. please refer to the related bug 17380 for more information.
Created attachment 13412 [details] updated ebuild, with sandbox fix
Created attachment 13413 [details, diff] required patch for updated ebuild