From owner-freebsd-ports@FreeBSD.ORG  Wed Jan 12 14:20:38 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 8476A16A4CF
	for <freebsd-ports@freebsd.org>; Wed, 12 Jan 2005 14:20:38 +0000 (GMT)
Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 33FF143D60
	for <freebsd-ports@freebsd.org>; Wed, 12 Jan 2005 14:20:38 +0000 (GMT)
	(envelope-from marko@freebsd.org)
Received: from [80.229.231.20] (helo=[192.168.254.25])
	by ptb-relay02.plus.net with esmtp (Exim) id 1CojMT-000N7l-7i;
	Wed, 12 Jan 2005 14:20:37 +0000
Message-ID: <41E532C6.20703@freebsd.org>
Date: Wed, 12 Jan 2005 14:23:02 +0000
From: Mark Ovens <marko@freebsd.org>
User-Agent: Mozilla Thunderbird 7.0 (X11/20050110)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Tigeot <ftigeot@wolfpond.org>
References: <41CAAA60.2080001@freebsd.org>
	<20041226171434.GA2658@aoi.wolfpond.org>
In-Reply-To: <20041226171434.GA2658@aoi.wolfpond.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-ports@freebsd.org
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2005 14:20:38 -0000

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
>> 
>> This used to work with previous versions of FreeBSD 5.x and digikam 
>> although I don't know when it stopped working.
>> 
>> I can't find a PR for this so I'm guessing it may be something specific 
>> to my system.
>> 
>> Can anyone shed any light on this please?
> 
> 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
> 

Francois,

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 hope you have better luck!

Regards,

Mark