View previous topic :: View next topic |
Author |
Message |
Joseph_sys Advocate
Joined: 08 Jun 2004 Posts: 2712 Location: Edmonton, AB
|
Posted: Fri Dec 28, 2012 2:02 am Post subject: gconf - failed: not writable |
|
|
trying to emerge: gnome-base/gconf-2.32.4
and I'm getting a strange error:
Code: | >>> '/var/log/portage/gnome-base:gconf-2.32.4:20121228-015444.log'
>>> Jobs: 6 of 29 complete, 1 failed Load avg: 3.08, 1.37, 0.57
* Package: gnome-base/gconf-2.32.4
* Repository: gentoo
* Maintainer: gnome@gentoo.org
* USE: amd64 elibc_glibc gtk introspection kernel_linux ldap policykit userland_GNU
* FEATURES: sandbox
ACCESS DENIED open_wr: /root/.gconf/.testing.writeability
ACCESS DENIED unlink: /root/.gconf/.testing.writeability
(gconftool-2:17733): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible
* Fixing OMF Makefiles ...
[ ok ]
* Disabling deprecation warnings ...
[ ok ]
* Running elibtoolize in: GConf-2.32.4/
* Applying portage/1.2.0 patch ...
* Applying sed/1.5.6 patch ...
* Applying as-needed/2.2.6 patch ...
* Applying gconf-2.24.0-no-gconfd.patch ...
[ ok ]
* Applying gconf-2.28.0-entry-set-value-sigsegv.patch ...
[ ok ]
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE "/var/log/sandbox/sandbox-17704.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 |
There aren't any files named: /root/.gconf/.testing.writeability
What is the solution? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21644
|
Posted: Fri Dec 28, 2012 2:21 am Post subject: |
|
|
This is a bug in the upstream build system, which the ebuild needs to workaround. The upstream build system is improperly trying to write to the live filesystem. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|