Re: pyrenamer gives 'Attempt to unlock mutex that was not locked'

[sp113438 <sp113438@telfort.nl>]

On Mon, 06 Oct 2014 14:19:55 +0200
Thilo <debian@matbox.de> wrote:

> Hi all,
> 
> please find my approach to resolving the issue of "Attempt to unlock
> mutex that was not locked" in the quoted emails below. The short
> answer is that this error is caused by improper use of glib
> threading. Such handling may have remained unnoticed up until now due
> to changes in the recent glib (2.42). Debian unstable/testing has
> been migrating from version 2.40 to 2.42 which is now causing this
> message in several codes.
> 
> Best regards
> Torsten

Thanks for your quick answer.

I guess I have to wait for a solution in Sid.

I will check on a daily basis.