I was installing gnome3 for the first time. The compile failed with ACCESS VIOLATION SUMMARY followed by a bunch of errors: F: open_wr S: deny P: /root/.gconf/.testing.writeability A: /root/.gconf/.testing.writeability R: /root/.gconf/.testing.writeability C: /usr/libexec/gconfd-2 F: unlink S: deny P: /root/.gconf/.testing.writeability A: /root/.gconf/.testing.writeability R: /root/.gconf/.testing.writeability C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state A: /root/.gconfd/saved_state R: /root/.gconfd/saved_state C: /usr/libexec/gconfd-2 F: open_wr S: deny P: /root/.gconfd/saved_state.tmp A: /root/.gconfd/saved_state.tmp R: /root/.gconfd/saved_state.tmp C: /usr/libexec/gconfd-2 Reproducible: Always Steps to Reproduce: 1. compile media-libs/gst-plugins-base-0.10.32 with standard feature 2. 3. Actual Results: sandbox access violation Expected Results: the ebuild do not try to read / write outside it's sandbox
Created attachment 273889 [details] build log, with color escapes
I did an emerge --resume, just in case, and it compiled successfully.. this is weird..
Is this still valid?
(In reply to comment #3) > Is this still valid? I've been able to install Gnome3 later on but I think an investigation on why the compile of gnome3 did try to write in the root home directory should be done before closing this bug it may as well be already been fixed by that time, it's up to you to decide what to do :) I never had that error again.
Looks solved as I couldn't find any duplicate of this for gnome-overlay (in main tree looks to work fine for me)