Date: Wed, 12 Jan 2005 21:38:10 +0100 From: Francois Tigeot <ftigeot@wolfpond.org> To: Mark Ovens <marko@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Digikam broken? Mutex lock failure Message-ID: <20050112203810.GA1892@aoi.wolfpond.org> In-Reply-To: <41E532C6.20703@freebsd.org> References: <41CAAA60.2080001@freebsd.org> <20041226171434.GA2658@aoi.wolfpond.org> <41E532C6.20703@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 12, 2005 at 02:23:02PM +0000, Mark Ovens wrote: > Francois Tigeot wrote: > >On Thu, Dec 23, 2004 at 11:22:08AM +0000, Mark Ovens wrote: > >>digikam-0.7 > >> > >>FreeBSD redshift 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed Dec 22 13:16:53 > >>GMT 2004 mark@redshift:/usr/obj/usr/src/sys/REDSHIFT i386 > >> > >>When I select my camera, Canon Powershot A70, from the Camera menu I get > >>these errors: > >> > >>Mutex lock failure: Resource deadlock avoided > >>Mutex unlock failure: Operation not permitted > >> > >Well, it seems to be more general: I have a similar problem here. > >(5.3-RELEASE-p2/amd64) > > > >The errors are a bit different: > > > >/libexec/ld-elf.so.1: /usr/X11R6/lib/libqt-mt.so.3: Undefined symbol > >"pthread_attr_init" > >Mutex destroy failure: Device busy > >ICE default IO error handler doing an exit(), pid = 58057, errno = 2 > > > I don't know if you've got digikam working yet but I found this > <http://frontrangebsd.org/pipermail/kde-freebsd/2004-December/009990.html>; > which should fix it for you - just need to cvsup your ports tree and > rebuild. > > It got rid of the mutex errors for me but I still get "Can't connect to > camera" in digikam itself :-( I rebuilt digikam today, still no change. The gui appears to run fine for a moment and crash when I select the camera. Since gphoto works for me, I can wait for the pthread stuff to be properly sorted on amd64... -- Francois Tigeot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050112203810.GA1892>