Summary: | Accessing /root/.gnome2 causes sandbox violations | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | john s j anderson <jacobs> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dark.elixir, dulmandakh, henrique.ferreiro, jakub, jorge.vargas, metalgod, simon.strandman |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | config.log from failed build |
Description
john s j anderson
2006-03-31 12:48:57 UTC
This is invalid banshee needs /root.gnome2 to install all stuff it needs. This is not a bug. btw... if you don't know how to assign bugs please don't do it gnome doesn't have nothing to do with it. Thanks anyway. resolved as invalid. (In reply to comment #1) > This is invalid banshee needs /root.gnome2 to install all stuff it needs. This > is not a bug. Gosh, then maybe portage shouldn't blow up with a sandbox violation, and tell me to report stuff to bugs.gentoo.org, because that sure makes it sound like a bug. It's also odd that after the build succeeds, I can 'rmdir /root/.gnome2' -- that is, the build doesn't actually *leave* anything in it. > btw... if you don't know how to assign bugs please don't do it gnome doesn't > have nothing to do with it. Sorry for the wrong guess on where to assign the bug. don't reopen the bug that's something i can't fix. Lots of apps needs that subdir to install correctly don't remove it. That dir is created because it's needed at build time. (In reply to comment #4) > don't reopen the bug that's something i can't fix. Lots of apps needs that > subdir to install correctly don't remove it. That dir is created because > it's needed at build time. Well, it's still a bug, regardless of whether you know how to fix it. Let me quote <http://dev.gentoo.org/~plasmaroo/devmanual/general-concepts/sandbox/>, which says: >> All packages must build correctly when sandbox is active. You may want to look at <http://dev.gentoo.org/~plasmaroo/devmanual//appendices/common-problems/#handling-access-violations> As for "lots of apps" which need that directory, I've currently got over 1150 packages installed on the box where I'm seeing this error, according to 'equery list -i|wc -l', including all of KDE and Gnome -- and this is the first I've run into this error. Reclose it again if you want; I'm done trying to help here. Thanks anyway. I know all that issues but gnome2 eclass NEEDS that dir to build lots of apps without access violation errors. Everytime you remove /root/.gnome2 you are doing a mistake. I don't need to get help anywhere you just need to NOT remove /root/.gnome2. I'm sure you get more info about that issue on gnome2 eclass on older bugs. This doesn't have anything to do with banshee. (In reply to comment #6) > I know all that issues but gnome2 eclass NEEDS that dir to build lots of apps > without access violation errors. Everytime you remove /root/.gnome2 you are > doing a mistake. I don't need to get help anywhere you just need to NOT remove > /root/.gnome2. I'm sure you get more info about that issue on gnome2 eclass on > older bugs. This doesn't have anything to do with banshee. > Then you need to fix your eclass. Minimally: addwrite /root/.gnome2 Preferably: Fix gnome2 eclass using ebuilds to not need to write there. antarus this is not my problem i don't have anything to do with gnome2 if this user don't remove /root/.gnome2 this access violations doesn't happen period. I'm closing this again if you want to reopen assign to gnome guys with a different sumary because this is not related to banshee at all. Ebuilds using /root as a dumpspace for crap suck, ebuilds that bomb out w/ sandbox violation if that crap is missing are plain broken. Ditto for Bug 118718, /root/.gstreamer-0.8 and /root/.gstreamer-0.10 need addwrite at least as well. No need for QA just yet. (In reply to comment #8) > antarus this is not my problem i don't have anything to do with gnome2 if this > user don't remove /root/.gnome2 this access violations doesn't happen period. This user didn't bloody *have* a /root/.gnome2 until he had to make one to get your ebuild to work. > I'm closing this again if you want to reopen assign to gnome guys with a > different sumary because this is not related to banshee at all. I'm not so sure about that. I grabbed the first ebuild I could find that uses the gnome2 eclass -- that was file-roller. It builds fine without /root/.gnome2, as you can see: ankh portage # ls -ald /root/.gnome2 ls: /root/.gnome2: No such file or directory ankh portage # emerge file-roller > /dev/null >>> Downloading http://gentoo.osuosl.org/distfiles/file-roller-2.12.3.tar.bz2 --17:24:46-- http://gentoo.osuosl.org/distfiles/file-roller-2.12.3.tar.bz2 => `/usr/portage/distfiles/file-roller-2.12.3.tar.bz2' Resolving gentoo.osuosl.org... 64.50.236.52, 64.50.238.52 Connecting to gentoo.osuosl.org|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 936,371 (914K) [application/x-tar] 100%[======================================================================================================================>] 936,371 1.03M/s 17:24:47 (1.03 MB/s) - `/usr/portage/distfiles/file-roller-2.12.3.tar.bz2' saved [936371/936371] >>> Regenerating /etc/ld.so.cache... ankh portage # ls -ald /root/.gnome2 ls: /root/.gnome2: No such file or directory ankh portage # grep inherit /usr/portage/app-arch/file-roller/file-roller-2.12.3.ebuild inherit eutils gnome2 Just another data point. that's strange... you should have /root/.gnome2 dir now i understand your point you simple didn't had root/.gnome2 at all (i thought you removed after it was created that's wrong). Well this is a job for gnome guys. what is the cvs revision id in /usr/portage/eclass/gnome2.eclass ? (3rd line from top) I don't see -given the ebuild & eclass combo- how this could happen. Also post the config.log from the builddir. Ok John let's see this... Please upgrade to banshee 0.10.9-r1 and see if you got the same issue (i made a little modification to avoid this problem). But again imo this should be on gnome2 eclass and not on the ebuild just like the gst stuff. Sorry if i sound harsh but i misunderstand what you were trying to say. My bad :(. Created attachment 83579 [details]
config.log from failed build
(In reply to comment #13) > what is the cvs revision id in /usr/portage/eclass/gnome2.eclass ? (3rd line > from top) <~> $ head /usr/portage/eclass/gnome2.eclass # Copyright 1999-2004 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/eclass/gnome2.eclass,v 1.68 2006/03/29 13:02:27 allanonjl Exp $ > Also post the config.log from the builddir. See attachment. (In reply to comment #14) > Please upgrade to banshee 0.10.9-r1 and see if you got the same issue Yep, blows up at same place, and creating the directory allows it to proceed. > Sorry if i sound harsh but i misunderstand what you were trying to say. My bad > :(. No worries. It turns out this is due a glib design choice http://bugzilla.gnome.org/show_bug.cgi?id=142568 . The quick and dirty solution for now is to allow writing of this dir. *** Bug 127651 has been marked as a duplicate of this bug. *** *** Bug 130061 has been marked as a duplicate of this bug. *** *** Bug 130781 has been marked as a duplicate of this bug. *** more specifically, you can look in gnome-vfs: libgnomevfs/gnome-vfs-init.c:64 (ensure_dot_gnome_exists) addwrite "${ROOT}/root/.gnome2" is now present in the eclass in cvs. *** Bug 126890 has been marked as a duplicate of this bug. *** *** Bug 142547 has been marked as a duplicate of this bug. *** |