From owner-freebsd-ports@FreeBSD.ORG Sat Jan 15 16:42:42 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8F1616A4CE; Sat, 15 Jan 2005 16:42:42 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84C4643D1D; Sat, 15 Jan 2005 16:42:37 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0FGgZW9007633; Sat, 15 Jan 2005 17:42:36 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0FGgcfw042069; Sat, 15 Jan 2005 17:42:38 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id j0FGgcqB042068; Sat, 15 Jan 2005 17:42:38 +0100 (CET) (envelope-from ftigeot) Date: Sat, 15 Jan 2005 17:42:38 +0100 From: Francois Tigeot To: Michael Nottebrock Message-ID: <20050115164238.GA38678@aoi.wolfpond.org> References: <41CAAA60.2080001@freebsd.org> <20041226171434.GA2658@aoi.wolfpond.org> <41E532C6.20703@freebsd.org> <20050112203810.GA1892@aoi.wolfpond.org> <41E76E5E.1050804@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E76E5E.1050804@gmx.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@freebsd.org cc: Mark Ovens Subject: Re: Digikam broken? Mutex lock failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 16:42:43 -0000 On Fri, Jan 14, 2005 at 08:01:50AM +0100, Michael Nottebrock wrote: > Francois Tigeot wrote: > > > >I rebuilt digikam today, still no change. The gui appears to run fine for > >a moment and crash when I select the camera. > > Look at (or save) the build output of digikam. If you have anything saying > "--as-needed" in there, you didn't cvsup or didn't cvsup the needed parts > of the ports-tree (the change is in Mk/bsd.kde.mk). I have just rebuilt digikam once more. I have no trace of "--as-needed" in the build log file; my bsd.kde.mk is version 1.48. When I launch digikam, the main window appears normally. Howewer, selecting an option in the menus result quite rapidly (2-3 seconds) in a non-responsive window. It isn't just the camera selection as I previously thought; most menu items give the same result. When I kill the application, this messages appear in the terminal window : Mutex destroy failure: Device busy ICE default IO error handler doing an exit(), pid = 42052, errno = 2 The binary is linked to libpthread.so.1: $ ldd /usr/local/bin/digikam | grep pthrea libpthread.so.1 => /usr/lib/libpthread.so.1 (0x804202000) I tried to remap libpthread to libthr with libmap.conf but the symptoms didn't change. -- Francois Tigeot