Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Attempt to unlock mutex that was not locked

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
User avatar
sjukfan
Posts: 386
Joined: 2010-03-01 19:39

Attempt to unlock mutex that was not locked

#1 Post by sjukfan »

After an update to GLib in Jessie the other day some/a lot of program may exit with the message Attempt to unlock mutex that was not locked. This is because of change in how GLib handles unlocking of non locked mutex.
Since GLib ≥ 2.41, attempting to release an unlocked mutex will abort(), as it happens on most systems already.
https://mail.gnome.org/archives/commits ... 08240.html

Some packages are already updated but file a bug report if you find one that hasn't been reported yet.
https://www.debian.org/Bugs/
Last edited by sjukfan on 2014-10-02 11:12, edited 1 time in total.
Bullseye amd64, AMD Ryzen 5 3600
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX

User avatar
sjukfan
Posts: 386
Joined: 2010-03-01 19:39

Re: Attempt to unlock mutex that was not locked

#2 Post by sjukfan »

Some packages have been updated but the updated versions are still in Sid. Some of these are
* SpaceFM
* pidgin-skype
Bullseye amd64, AMD Ryzen 5 3600
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX

Post Reply