Bug 118028 – Sandbox violation with xscreensaver 4.23

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Heath Holcomb 2006-01-06 05:45:22 UTC]

Upgrading xscreensaver-4.22-r4 to xscreesaver-4.23 produces a sandbox violation
on my system:

$ emerge -v xscreensaver

... ( lots of normal compilation messages snipped )
make[1]: Leaving directory `/var/tmp/portage/xscreensaver-4.23/work/xscreensaver-4.23/hacks/glx'
make[1]: Entering directory `/var/tmp/portage/xscreensaver-4.23/work/xscreensaver-4.23/po'
/usr/bin/gmsgfmt -o ca.gmo ca.po
/usr/bin/gmsgfmt -o da.gmo da.po
/usr/bin/gmsgfmt -o de.gmo de.po
/usr/bin/gmsgfmt -o es.gmo es.po
/usr/bin/gmsgfmt -o et.gmo et.po
/usr/bin/gmsgfmt -o fi.gmo fi.po
/usr/bin/gmsgfmt -o fr.gmo fr.po
/usr/bin/gmsgfmt -o hu.gmo hu.po
/usr/bin/gmsgfmt -o it.gmo it.po
/usr/bin/gmsgfmt -o ja.gmo ja.po
/usr/bin/gmsgfmt -o ko.gmo ko.po
/usr/bin/gmsgfmt -o nb.gmo nb.po
/usr/bin/gmsgfmt -o nl.gmo nl.po
/usr/bin/gmsgfmt -o no.gmo no.po
/usr/bin/gmsgfmt -o pl.gmo pl.po
/usr/bin/gmsgfmt -o pt.gmo pt.po
/usr/bin/gmsgfmt -o pt_BR.gmo pt_BR.po
/usr/bin/gmsgfmt -o ru.gmo ru.po
/usr/bin/gmsgfmt -o sk.gmo sk.po
/usr/bin/gmsgfmt -o sv.gmo sv.po
/usr/bin/gmsgfmt -o vi.gmo vi.po
/usr/bin/gmsgfmt -o wa.gmo wa.po
/usr/bin/gmsgfmt -o zh_CN.gmo zh_CN.po
/usr/bin/gmsgfmt -o zh_TW.gmo zh_TW.po
make[1]: Leaving directory `/var/tmp/portage/xscreensaver-4.23/work/xscreensaver-4.23/po'
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-x11-misc_-_xscreensaver-4.23-12314.log"

access_wr: /var/lib/rpm
access_wr: /var/lib/rpm
--------------------------------------------------------------------------------

Here is my emerge info

Portage 2.0.53 (default-linux/x86/2005.1, gcc-3.3.5-20050130, glibc-2.3.5-r2, 2.6.14.2 i686)
=================================================================
System uname: 2.6.14.2 i686 Intel(R) Xeon(TM) CPU 3.60GHz
Gentoo Base System version 1.12.0_pre12
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acpi alsa apm audiofile avi berkdb bitmap-fonts bzip2 cdr cjk crypt cups dbus dvd eds emboss encode esd ethereal exif expat fam firefox font-server foomaticdb fortran gdbm gif glut gnome gpm gstreamer gtk gtk2 hal howl imagemagick imap imlib ipv6 java jpeg lcms ldap libg++ libwww logrotate mad mikmod mng mp3 mpeg ncurses nethack nls nptl nsplugin ogg oggvorbis opengl oss pam pcre pdflib perl png python quicktime readline samba sdl spell ssl tcpd threads tiff truetype truetype-fonts type1-fonts udev vorbis xml2 xmms xscreensaver xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY

[Comment 1 Krzysztof Pawlik (RETIRED) 2006-01-08 13:16:34 UTC]

in "lots of normal compilation messages snipped" there should be error message - could you attach it too?

[Comment 2 Henryk Plötz 2006-01-08 17:19:03 UTC]

I had the same bug, and no, there was no specific error message among the compilation messages.

What is even more strange: I just tried to emerge it again and it worked. I compared the logfiles and they are virtually identical, up to the point where one says "ACCESS VIOLATION SUMMARY" and the other one installs into the temp directory. (Will attach both files.)

Between both tries I updated a lot of other packages and there might or might not be a relation.

[Comment 3 Henryk Plötz 2006-01-08 17:20:44 UTC]

Created attachment 76568 [details]
Log of a working xscreensaver compilation

[Comment 4 Henryk Plötz 2006-01-08 17:21:49 UTC]

Created attachment 76569 [details]
Log of a failing xscreensaver compilation

[Comment 5 Heath Holcomb 2006-01-09 05:44:54 UTC]

Created attachment 76615 [details]
xscreensaver build with sandbox violation

As Henryk said and as I originally mentioned, there are no error messages in the compilation output. I'm not sure why the ebuild would attempt to access /var/lib/rpm either. I do have RPM installed and I noticed that the xscreensaver tarball includes a specfile but have not really had time to look at the Makefiles.

[Comment 6 Andrea Bruna 2006-01-13 14:26:58 UTC]

(In reply to comment #0)
> Upgrading xscreensaver-4.22-r4 to xscreesaver-4.23 produces a sandbox violation
> on my system:

Same problem here... 

I had to unmerge rpm before upgrading to xscreensaver-4.23 

[Comment 7 Krzysztof Pawlik (RETIRED) 2006-01-13 15:30:13 UTC]

Created attachment 77035 [details, diff]
xscreensaver-4.23-norpm.patch

Could you test if applying that patch helps? In the ebuild change the line:

epatch ${FILESDIR}/${PN}-4.22-configure.patch

to

epatch ${FILESDIR}/${PN}-4.23-norpm.patch

[Comment 8 Krzysztof Pawlik (RETIRED) 2006-01-15 04:59:25 UTC]

Fixed - should hit mirrors soon.