From owner-freebsd-gnome@FreeBSD.ORG Wed Sep 30 22:22:33 2009 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23F4F1065670 for ; Wed, 30 Sep 2009 22:22:33 +0000 (UTC) (envelope-from datahead4@gmail.com) Received: from mail-pz0-f194.google.com (mail-pz0-f194.google.com [209.85.222.194]) by mx1.freebsd.org (Postfix) with ESMTP id F0B118FC19 for ; Wed, 30 Sep 2009 22:22:32 +0000 (UTC) Received: by pzk32 with SMTP id 32so4775763pzk.3 for ; Wed, 30 Sep 2009 15:22:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=cyHedDzOOmzfNd8jpwXnMi1UjIlokoKnypC8RxK4Q8M=; b=UD1oV/9MKUwDKhh+dsWkQ5q808UTAMuWWdTUU1WA7a5SZ7gaLSL5XZeSpsHeM5Wjqw viKT6+ayyk3SoWK+GGptIrMUU/yLOFi5zC18w1/bq94QTmHDWmfwuhACxC9HXon/ILjH hJzEvpLD5jCz476HKAmIs2zl3O1Rztr8woLpY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=F6PtCUszR45yoBzd+uSNotBiI4i2+QUYYN7YkZjBgh/KCYpB1PR7RmXMIYYIfWn5gF 053XCyO39szhwN+k/m3Pa5qxltDIMiQOpWBl9gVotTOMLRUl6CDY8yCapli48fE2wTwX 8kIQFMCD0fYLdK1cytKR/ydbycIoz4oxlyG7w= MIME-Version: 1.0 Received: by 10.114.69.19 with SMTP id r19mr558234waa.117.1254347965456; Wed, 30 Sep 2009 14:59:25 -0700 (PDT) Date: Wed, 30 Sep 2009 16:59:25 -0500 Message-ID: From: Matt To: FreeBSD GNOME Users Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: pthread_mutexattr_settype assertion from PulseAudio with Amarok 2.2 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2009 22:22:33 -0000 Does anyone know if the root cause of the "Assertion =E2=80=98pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) =3D=3D 0= =E2=80=B2 failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). Aborting." error discussed at: http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/ was ever determined? I'm seeing this same error when trying to update the amarok-kde4 port to version 2.2 and the only discussion I can find related to this issue is at http://lists.freebsd.org/pipermail/freebsd-gnome/2009-July/022732.html and I don't see a resolution. Relevant data about my system: - All ports built in Tinderbox with "WITH_DEBUG=3Dyes" set - Tinderbox jail is 8-STABLE from 2009-09-10 16:42:33 - Tinderbox ports were updated 2009-09-14 12:59:10 - System where ports are installed is same host running the Tinderbox. "uname -a" states (sanitized) "FreeBSD 8.0-RC1 FreeBSD 8.0-RC1 #0: Mon Sep 21 09:46:16 CDT 2009 root@:/usr/obj/usr/src/sys/CUSTOM i386" - pkg_info list available at http://freebsd-gnome.pastebin.com/m1b0d9c9f I can't seem to get any usable core dumps from the system, but I can provide ktrace or other output if anyone is interested. Thank you, Matt