After last emerge --sync, a gconf update fails and shows this error message: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE "/var/log/sandbox/sandbox-15836.log" VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /root/.gconf/.testing.writeability A: /root/.gconf/.testing.writeability R: /root/.gconf/.testing.writeability C: /usr/bin/gconftool-2 --shutdown F: unlink S: deny P: /root/.gconf/.testing.writeability A: /root/.gconf/.testing.writeability R: /root/.gconf/.testing.writeability C: /usr/bin/gconftool-2 --shutdown -------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge -DuvaN world 3. See the error Actual Results: Gconf don't compile Expected Results: Gconf compiling OK
Created attachment 333528 [details] I get a similar error. Seems it wants write permissions in /root/
Just to make this bug report a little more complete, here are the two versions I tried that have this bug: - =gnome-base/gconf-2.32.4 - =gnome-base/gconf-3.2.5
I can't reproduce the problem on my machine :/ People who are experiencing this, please attach the output of "emerge --info gconf" and "ps aux | grep gconfd"
I've moved kill_gconf back to pkg_setup() in the gconf ebuilds. Please check if that fixes the problem. (Wait until ~00:30 utc to make sure the fix arrives at your local rsync mirror.) + 27 Dec 2012; Alexandre Rostovtsev <tetromino@gentoo.org> gconf-2.32.4.ebuild, + gconf-3.2.5.ebuild: + Move kill_gconf to pkg_setup in an attempt to fix access violations + experienced by some users (bug #448952; thanks to iamben for the suggested + solution).
After a re-sync, gconf compiles and installs without the sandbox access violation I experienced earlier today.
Also works for me. Thanks.
(In reply to comment #5) > After a re-sync, gconf compiles and installs without the sandbox access > violation I experienced earlier today. +1