dbus is a dependancy for gnome 2.8 so this should probably be fixed before 2.8 gets unmasked. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-sys-apps_-_dbus-0.22-r1-30117.log" mkdir: /root/.kde mkdir: /root/.kde mkdir: /root/.kde mkdir: /root/.kde -------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51_rc1 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040619-r0, 2.6.8-gentoo-r2 i686) ================================================================= System uname: 2.6.8-gentoo-r2 i686 Intel(R) Pentium(R) III Mobile CPU 1200MHz Gentoo Base System version 1.4.16 distcc 2.14 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -mmmx -msse -mfpmath=sse -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -mmmx -msse -mfpmath=sse -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts avi berkdb bitmap-fonts cdr crypt cups encode esd foomaticdb gdbm gif gnome gnome2 gpm gtk gtk2 guile hal imlib jpeg kde libg++ libwww mad mikmod mmx motif mozilla mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl see slang spell ssl svga tcpd tetex truetype x86 xml2 xmms xprint xv zlib"
Thanks for the bug report, but sys-apps/dbus-0.22-r1 merges fine for me using the same USE flags. Please post the logfile (/tmp/sandbox-sys-apps_-_dbus-0.22-r1-30117.log) as an attachment. Portage 2.0.51_rc1 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.9-rc2 i686) ================================================================= System uname: 2.6.9-rc2 i686 Intel(R) Pentium(R) M processor 1.70GHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://mirror.pacific.net.au/gentoo http://mirror.pacific.net.au/linux/Gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="X acpi alsa apache2 avi bcmath berkdb bitmap-fonts bzlib caps cdr crypt cups divx4linux doc dvd encode fam gd gdbm gif gnome gpm gtk gtk2 guile imap imlib java jikes jpeg ldap libwww mad memlimit mmx motif mozilla mpeg ncurses offensive oggvorbis opengl pam pdflib perl png python quicktime readline samba sdl slang spell sse ssl svg svga tcltk theora tiff truetype x86 xml2 xmms xprint xv zlib"
The log file only had the same thing as the sandbox error in it. -- mkdir: /root/.kde mkdir: /root/.kde mkdir: /root/.kde mkdir: /root/.kde -- I did an emerge with FEATURES="-sandbox" and it only created some empty directories under /root/.kde. I wonder if it's only creating those directories if they don't already exist. By any chance do you already have a /root/.kde? If so, maybe you could try removing/renaming it and re-emerging.
No, I don't have an existing /root/.kde I didn't see "qt" in your USE flags, meaning the ebuild passes --disable-qt to configure and hence dbus shouldn't be messing with qt/kde stuff at all. Please post the full output of "emerge sys-apps/dbus" as an attachment.
Created attachment 40434 [details] emerge log
You are correct that 'qt' was removed from my USE flags.
Turns out that ~/.kde/share/config is created when kde-config is run. This has previously been the cause of sandbox violations in various qt/kde ebuilds, and there is a workaround in the kde eclass. The part I still don't understand is why the sandbox violation isn't occuring on my machine, and why kde-config is even being called during the build (perhaps it isn't)! A simple "fgrep -R kde-config" in the build dir shows that kde-config is only called explicitly in configure, so I would expect the sandbox violation to occur then, and occur on my machine as well.
I had kde-base/kdelibs-3.0.5a on my system so I upgraded to kde-base/kdelibs-3.3.0. dbus will now emerge cleanly. The wierd thing is that kde-config itself hasn't changed size/checksum. moaiki root # ls -la kde-config -rwxr-xr-x 1 root root 12948 Sep 26 04:59 kde-config moaiki root # ls -la /usr/kde/3/bin/kde-config -rwxr-xr-x 1 root root 12948 Jan 4 2003 /usr/kde/3/bin/kde-config moaiki root # md5sum kde-config 6c758588c8ce943cbafef710541beaba kde-config moaiki root # md5sum /usr/kde/3/bin/kde-config 6c758588c8ce943cbafef710541beaba /usr/kde/3/bin/kde-config So I'm still puzzeled as to what the issue is. Why is kde-config being run with USE="-qt"? Perhaps the easist thing to do is to have the ebuild print some instructions about upgrading kdelib if you get a sandbox error.
thats probably not the reason it works now. kde team : what is the solution here ?
If you can't find a configure option to bypass that step, then you can: REALHOME="$HOME" mkdir -p $T/fakehome/.kde mkdir -p $T/fakehome/.qt export HOME="$T/fakehome" in the ebuild.
The QT bindings are disabled for now.
