From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 11:17:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E84416A4CE for ; Sat, 17 Jan 2004 11:17:41 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56A7A43D31 for ; Sat, 17 Jan 2004 11:17:40 -0800 (PST) (envelope-from wendy.humphrey@comcast.net) Received: from [192.168.8.100] (12-212-101-52.client.attbi.com[12.212.101.52]) by comcast.net (rwcrmhc13) with SMTP id <2004011719173901500keg12e>; Sat, 17 Jan 2004 19:17:39 +0000 From: Brendon and Wendy To: freebsd-current@freebsd.org Content-Type: text/plain Message-Id: <1074367054.666.7.camel@bigboot.humphrey.world> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 17 Jan 2004 11:17:34 -0800 Content-Transfer-Encoding: 7bit Subject: Last nights current killed totem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 19:17:41 -0000 Dear List, Last night I built world/kernel wit 5.2-current cvsupped at 0400 PDT. For some reason or other this build seems snappier than a recent current. Nice. However, I've noticed that running totem (gnome media player) now locks the machine hard. I dont know if it was the kernel or the threading libraries, or perhaps some other change that caused this. xmms still works, haven't tried mplayer or xine (what totem is based on). Will later. I do use the NVIDIA drivers, but that is nothing new for me, so shouldn't have necessarily influenced this. I would have been using the default thread library (whatever that is) due to empty libmap.conf file. Any ideas? Cheers, Brendon