Date: Sat, 15 Jan 2005 17:42:38 +0100 From: Francois Tigeot <ftigeot@wolfpond.org> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: Mark Ovens <marko@freebsd.org> Subject: Re: Digikam broken? Mutex lock failure Message-ID: <20050115164238.GA38678@aoi.wolfpond.org> In-Reply-To: <41E76E5E.1050804@gmx.net> References: <41CAAA60.2080001@freebsd.org> <20041226171434.GA2658@aoi.wolfpond.org> <41E532C6.20703@freebsd.org> <20050112203810.GA1892@aoi.wolfpond.org> <41E76E5E.1050804@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050115164238.GA38678>