moving /etc/gconf/gconf.xml.mandatory/ away from its place (or remove it) emerge gconf will sometime during the ebuild gconf install ; attempt to re-create this directory. the sandbox will catch two mkdir, but, grepping the install log will not show any command actually creating the part. there is a few lines in install-data-local that could / should do it but they adhere (DESTDIR) so thats not it.... I'm kindof stumped here and hope you'll come up with some ideas
Spider, I've noticed that the cause of those sandbox violations is not the compilation nor installation process. The problem is created inside the `kill-gconf' function, which attempts to shutdown any running gconf daemons with the gconftool[-*] tools. Try to (re)move /etc/gconf/gconf.xml.mandatory and run any of the following commands: /usr/bin/gconftool --shutdown /usr/bin/gconftool-1 --shutdown Aha! Now, I'm not really sure about what would be the best solution here. I think a couple of choices could be: - Disable the sandbox feature inside kill_gconf, on purpose. - Eliminate kill_gconf entirely (actually, I don't fully understand why it was created in the first place.) Please let me know your thoughts about this, See you around
Actually the reason was quite simple... if the user(any user) had a gconf process running it would overwrite the new gconf subdirs and give a configuration conflict as the old daemon wrote its old data over the freshly installed one.
