Summary: | media-libs/swfdec-0.6.2: Sandbox violations | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | ed, graham, ian, njdoyle+bugs, paulo, pclouds, portage |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 214260 | ||
Attachments: | swfdec-0.6.2.ebuild |
Description
Alexander Skwar
2008-04-03 09:22:32 UTC
Compiling swfdec with USE=-gstreamer "fixes" the problem. Compiling swfdec with USE="-doc" also "fixes" the problem! Here's a snippet of build output on my system: creating swfdec-scan gtk-doc: Running scanner swfdec-scan ACCESS DENIED open_wr: /root/.gstreamer-0.10/registry.x86_64.xml.tmp3PKV8T ACCESS DENIED open_wr: /root/.gstreamer-0.10/registry.x86_64.xml.tmp1JIV8T touch scan-build.stamp make[2]: vfork: Invalid argument make[2]: Leaving directory `/var/tmp/portage/media-libs/swfdec-0.6.2/work/swfdec-0.6.2/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/swfdec-0.6.2/work/swfdec-0.6.2' make: *** [all] Error 2 I re-emerged gtk-doc (dev-util/gtk-doc-1.10-r1) and that allowed swfdec to build successfully with both the 'doc' and 'gstreamer' use flags. (In reply to comment #3) > I re-emerged gtk-doc (dev-util/gtk-doc-1.10-r1) and that allowed swfdec to > build successfully with both the 'doc' and 'gstreamer' use flags. > re emerging gtk-doc had no effect for me. It still shows the same sandbox violations. (In reply to comment #4) > (In reply to comment #3) > > I re-emerged gtk-doc (dev-util/gtk-doc-1.10-r1) and that allowed swfdec to > > build successfully with both the 'doc' and 'gstreamer' use flags. > > > > re emerging gtk-doc had no effect for me. It still shows the same sandbox > violations. Sorry, re-emerging gtk-doc tuned out to be a red herring! What actually allowed me to emerge swfdec successfully was running the following commands after it failed: cd /var/tmp/portage/media-libs/swfdec-0.6.2/work/swfdec-0.6.2/doc make clean make and then emerging swfdec again. This is not a valid fix as it leaves mess behind in the /root directory, and besides, it's easier to emerge with FEATURES="-sandbox" (also not a valid fix of course). swfdec-scan is linked to libgstreamer and libgconf. As a result, when these libraries are intialized, they try to access /root. Setting GST_REGISTRY (for example to /tmp/registry.xml) will avoid gstreamer access violation. gconf violation is more difficult though. Created attachment 148760 [details] swfdec-0.6.2.ebuild Please try the attached ebuild. The diff is diff --git a/media-libs/swfdec/swfdec-0.6.2.ebuild b/media-libs/swfdec/swfdec-0.6.2.ebuild index 54b3aaf..f5c028b 100644 --- a/media-libs/swfdec/swfdec-0.6.2.ebuild +++ b/media-libs/swfdec/swfdec-0.6.2.ebuild @@ -59,6 +59,12 @@ src_compile() { use alsa && myaudio="alsa" myconf=" --with-audio=$myaudio" + # bug #216009 + # avoid writing to /root/.gstreamer-0.10/registry.xml + export GST_REGISTRY="${T}"/registry.xml + # also avoid loading gconf plugins, which may write to /root/.gconfd + export GST_PLUGIN_SYSTEM_PATH="${T}" + econf \ $(use_enable doc gtk-doc) \ $(use_enable gstreamer) \ I cleaned out the the files left behind in the /root directory from my earlier experiments (to start with a clean slate) and tried Nguyen Thai Ngoc Duy's patched ebuild. It worked for me! FTR, here are my USE flags for the ebuild: [ebuild R ] media-libs/swfdec-0.6.2 USE="alsa doc gstreamer gtk mad -ffmpeg -oss -pulseaudio" 0 kB Thanks for the fix! Please mark as blocking bug 214260. I'm waiting for at least one more user confirming this bug is fixed before I commit it. So please test. Confirm ebuild fixes bug here. InCVS *** Bug 216575 has been marked as a duplicate of this bug. *** |