| View previous topic :: View next topic |
| Author |
Message |
all-inc.
Tux's lil' helper
Joined: 03 Jul 2004
Posts: 138
Location: Darmstadt.Germany.EU
|
 Posted: Tue May 30, 2006 7:17 pm Post subject: emerge captive fails; sanbox "ACCESS VIOLATION" SO |
 |
|
The problem is solved, see above for the resolution
hi,
just tried to upgrade my captive to version 1.1.7-r1. when compiling is finished, the following sandbox errormessage occurs:
| Code: | make[2]: Leaving directory `/var/tmp/portage/captive-1.1.7-r1/work/captive-1.1.7/po'
make[2]: Entering directory `/var/tmp/portage/captive-1.1.7-r1/work/captive-1.1.7'
make[2]: Für das Ziel »all-am« ist nichts zu tun.
make[2]: Leaving directory `/var/tmp/portage/captive-1.1.7-r1/work/captive-1.1.7'
make[1]: Leaving directory `/var/tmp/portage/captive-1.1.7-r1/work/captive-1.1.7'
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-sys-fs_-_captive-1.1.7-r1-23750.log"
chmod: /root/.gnome2_private
chmod: /root/.gnome2_private
[NOTE: and the following in the log file, when i rename the /root/.gnome2_private dir before emerging: ]
mkdir: /root/.gnome2_private (symlink to /root/)
mkdir: /root/.gnome2_private (symlink to /root/)
-------------------------------------------------------------------------------- |
my portage, bash and sandbox packages are up-2-date (stable releases): portage-2.0.54-r2 bash-3.1_p16 sandbox-1.2.17
kernel release(x86): 2.6.12-gentoo-r6 (i know, not brand knew, i'm a little bit lazy in the last few months...ABITUR)
if you need more information in order to help me, just let me know(e.g. emerge --info [--verbose] ).
thank you... and don't be angry if there's already help out there for this problem...i didn't find in my short researches yet! imho this is a general bug in the actual captive-1.1.7-r1 emerge, isn't it? 
thank you for help!
-Sebastian
_________________
# make config; not war
registered linux user # 265707
Last edited by all-inc. on Thu Jun 01, 2006 4:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
Philantrop
Retired Dev
Joined: 21 Dec 2004
Posts: 1130
Location: Germany
|
| Posted: Tue May 30, 2006 7:25 pm Post subject: |
|
|
Yes, it's a bug in the ebuild and you're not alone:
https://bugs.gentoo.org/show_bug.cgi?id=133357
If you just want to get over with it disable the sandbox feature for this emerge:
| Code: | | FEATURES="-sandbox" emerge captive |
(The nitpickers are now going to tell us we don't need the quotation marks but they don't hurt and it's good practice to use them.) |
|
| Back to top |
|
|
all-inc.
Tux's lil' helper
Joined: 03 Jul 2004
Posts: 138
Location: Darmstadt.Germany.EU
|
| Posted: Tue May 30, 2006 7:43 pm Post subject: |
|
|
oh, i'm very sorry ^^ didn't take a look in bugzilla!
but thank you for your fast response...
yes, this simple FEATURES="-sandbox" trick already came into my mind, but i didn't want to take this workaround because... i'm wondering why the hell the ebuild is playing with my .gnome2_private directory?! it hasn't neither a special meaning for captive nor is it the top literal directory(i thought, this was perhaps some weird scripting-batch-process-whatever problem, but i renamed the dir and this was proved to be the wrong idea...)
this doesn't make sense for me and i don't feel comfortable while sandbox is disabled...
but perhaps i'm too paranoid and i should just take this workaround and be happy.
i hope this will be solved soon...strange 
[EDIT] OK i emerged with disabled sandbox...when i try to mount a ntfs partition, the following error occurs 
| Code: | 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!).
argh, not a good workaround...
cya sebastian
_________________
# make config; not war
registered linux user # 265707 |
|
| Back to top |
|
|
all-inc.
Tux's lil' helper
Joined: 03 Jul 2004
Posts: 138
Location: Darmstadt.Germany.EU
|
| Posted: Thu Jun 01, 2006 4:25 pm Post subject: Solved |
|
|
ok, i (better, someone else with me 2gether) solved the problem you can take a look at the bug link mentioned before or read the above stuff:
you have to edit some lines in the captive ebuild.
'diff captive-1.1.7-r1.ebuild.orig captive-1.1.7-r1.ebuild' shows:
| Code: |
46a47,52
> # Do not remove the addwrite. bug #128289, bug #133357
> addwrite "${ROOT}/root/.gnome2"
> addwrite "${ROOT}/root/.gnome2_private"
> addwrite "${ROOT}/root/.gconfd"
> addwrite "${ROOT}/root/.gconf"
> |
then, run | Code: | | ebuild /usr/portage/sys-fs/captive/captive-1.1.7-r1.ebuild digest |
and everything should be fine.
thank u again, Sebastian
_________________
# make config; not war
registered linux user # 265707 |
|
| 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
|
|
Portage & Programming
