>>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-sys-fs_-_captive-1.1.7-r1-14901.log" chmod: /root/.gnome2_private chmod: /root/.gnome2_private -------------------------------------------------------------------------------- posted this to forums a while back, no responce , no fix , so let's make it official.
exactly the same problem here, also posted in forum, but the given workaround didn't solve the problem (for me). have a look http://forums.gentoo.org/viewtopic-t-466896.html suggested workaround: FEATURES="-sandbox" emerge captive results in: ---------- yuna1 root # mount -t captive-ntfs /dev/hda2 /mnt/win /usr/libexec/captive-sandbox-server: lstat/stat("/") of chroot path component has UID 500 !=0! Aborting! Captive-ERROR **: Error connecting to the sandbox server (failed "data_size>=1"). Try running by hand: /usr/libexec/captive-sandbox-server aborting... ---------- when running captive-sandbox-server by hand, the first message error shows up(UID 500!=0!). i played a little bit with strace to find out, to which path this error refers...without success. any help, solutions?
I added an addwrite as advertised in the gnome2 eclass for the sandbox bug. Sebastian Stammler, can you please report your bug upstream to the captive mailing list if it still ahppens with the addwrite? --- /usr/portage/sys-fs/captive/captive-1.1.7-r1.ebuild 2006-06-01 16:38:28.000000000 +0200 +++ captive-1.1.7-r1.ebuild 2006-04-05 14:46:06.000000000 +0200 @@ -44,6 +44,9 @@ } src_compile() { + # Do not remove the addwrite. bug #128289, bug #133357 + addwrite "${ROOT}/root/.gnome2" + # disable some tests to save time ;) econf $(use_enable debug bug-replay) \ $(use_with readline) \
ok, i patched my captive ebuild, as you suggested... now i get new sandbox access violation errors, when i run 'emerge captive' ( i DON'T use FEATURES="-sandbox" now!): --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-sys-fs_-_captive-1.1.7-r1-29120.log" open_wr: /root/.gconf/.testing.writeability unlink: /root/.gconf/.testing.writeability open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state.tmp --------------------------------------------------------------------------------
if you use addwrite /root/.gnome2_private /root/.gnome2 /root/.gconfd /root/.gconf does it work better then?
hmm if i would know the exact meaning of the addwrite command, perhaps i would have tried this on my own... it isn't explained in the gentoo ebuild developer's handbook. ok, i guess, it has something to do with sandbox, to add write permission to the given files/folders... back to the problem: with that, i can now emerge the whole thing without disabling sandbox! but i still get the same problem as mentioned berfore, when i try to mount my ntfs partition... "/usr/libexec/captive-sandbox-server: lstat/stat("/") of chroot path component has UID 500 !=0!" but that's another problem, has nothing to do with this bug, so thank you! now i start solving this problem ;) cya
I'M SORRY, my fault... for ANY REASON my / dir is really owned by userid 500 (my default user). LOL -_- now everything works fine!
I still get the errors: open_wr: /root/.gconf/.testing.writeability unlink: /root/.gconf/.testing.writeability open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state open_wr: /root/.gconfd/saved_state
that cant be, I added "addwrite" for all those. IN what ebuild phase do you get the errors? Can you attach the full build log? emerge captive > log
this is resolved - if not I neeed more info.
