If pygobject was built with libffi support, building totem will link the totem binary to libffi.so.4. This seems to cause totem to sometimes use memory management functions (such as malloc and free) from libffi instead of the ones from libc. This leads to immediate crashes. In particular, totem WILL crash when opening ANY file, and in fact, will usually crash when simply launching the "open file" dialog. I have recorded a dozen backtraces; the exact function where the segfault occurs is unpredictable, but in all cases, it's due to malloc/free going wrong at some point. And not linking totem to libffi.so.4 fixes the problem. I have only observed this problem on amd64; on my x86 machine, totem with libffi appears to work fine. To reproduce, on an amd64 machine: # USE="libffi" emerge gcc pygobject totem $ totem any-media-file.wav Multiple segmentation faults occurred; can't display error dialog To fix: # USE="-libffi" emerge gcc pygobject totem (*note: current pygobject configure is broken, and will link to libffi even if USE=-libffi, as long as gcc was build with libffi support. See bug 230751 ) # emerge --info Portage 2.2_rc1 (default-linux/amd64/2007.0/desktop, gcc-4.3.1, glibc-2.8_p20080602-r0, 2.6.25-gentoo-r6.10 x86_64) ================================================================= System uname: Linux-2.6.25-gentoo-r6.10-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q6600_@_2.40GHz-with-glibc2.2.5 Timestamp of tree: Fri, 04 Jul 2008 16:30:03 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r5 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.2.5 sys-apps/sandbox: 1.2.18.1-r3 sys-devel/autoconf: 2.13, 2.62-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.16.1-r3, 2.17-r2, 2.18-r2 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.4 virtual/os-headers: 2.6.25-r4 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/eselect/postgresql /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--with-bdeps=y" FEATURES="ccache distlocks parallel-fetch preserve-libs sandbox sfperms strict unmerge-orphans userfetch userpriv" GENTOO_MIRRORS="http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_US.utf8" LDFLAGS="-Wl,--as-needed -Wl,-O1" LINGUAS="en ru" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/auto-portage /usr/portage/local/layman/armagetron /usr/portage/local/layman/sunrise /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage"
Have you checked if you have more than one libffi installed in your system? Please look at: http://bugs.gentoo.org/show_bug.cgi?id=198925#c43
(In reply to comment #1) > Have you checked if you have more than one libffi installed in your system? > Please look at: > http://bugs.gentoo.org/show_bug.cgi?id=198925#c43 Thanks, you are right, I had a secont copy of libffi.so.4 coming in from g-wrap. Unmerging g-wrap fixed everything.
*** This bug has been marked as a duplicate of bug 198925 ***
