mintupdate: Attempt to unlock mutex that was not locked

Archived topics about LMDE 1 and LMDE 2
Locked
alobo
Level 1
Level 1
Posts: 38
Joined: Sun Jun 17, 2012 3:17 am

mintupdate: Attempt to unlock mutex that was not locked

Post by alobo »

I get the following error when I try to use mintupdate
in LMDE MATE:

$ glibtop: Non-standard uts for running kernel:
release 3.11-2-486=3.11.0 gives version code 199424

Attempt to unlock mutex that was not locked
Aborted

I think this has happened because I included this repo
http://http.debian.net/debian/ testing main contrib non-free
to install a program that I needed (qgis). It seems that
could have updated GLib from testing and that could have caused the problem.

Could anybody tell me the last GLib version that would not cause the mutex error? Perhaps I could just downgrade to it.

According to
http://forums.linuxmint.com/viewtopic.p ... 1&p=940644
the mutex issue has been solved with the 2.24.25-1 versions of libgtk, but
I just get 2.24.22-1 in my Synaptic.

Which would be the way to solve this mutex problem?

Thanks
py-thon
Level 4
Level 4
Posts: 315
Joined: Fri Sep 27, 2013 2:24 pm
Location: Paraguay

Re: mintupdate: Attempt to unlock mutex that was not locked

Post by py-thon »

Try again! Maybe you forgot to run update before checking with synaptic. Version 2.24.25-1 is in testing for some days now, at least in ftp.debian.org
Tower: Sparky 64 bit Mate+mintmenu - Netbook: Sparky 32 bit Mate+mintmenu
alobo
Level 1
Level 1
Posts: 38
Joined: Sun Jun 17, 2012 3:17 am

Re: mintupdate: Attempt to unlock mutex that was not locked

Post by alobo »

No luck, I run
sudo apt-get update
before starting synaptic.
Which repo should I have selected? I've been told several times not to use the debian testing in LMDE...
py-thon wrote:Try again! Maybe you forgot to run update before checking with synaptic. Version 2.24.25-1 is in testing for some days now, at least in ftp.debian.org
py-thon
Level 4
Level 4
Posts: 315
Joined: Fri Sep 27, 2013 2:24 pm
Location: Paraguay

Re: mintupdate: Attempt to unlock mutex that was not locked

Post by py-thon »

As you started with packages from testing you now have two possibilites:
1. Not use testing-repos and downgrade to what your system was before getting packages from testing. Turn back the clock so to say.
or
2. Use testing-repos one more time, update and upgrade the packages needed which are in

Code: Select all

deb http://ftp.debian.org/debian/ testing main contrib non-free
(actually they should all be in main).
But don't run a full upgrade or dist-upgrade with this repository activated. Just activate the testing-repo, download and install the necessary packages in synaptic and deactivate the testing-repo again.
Using synaptic you best sort packages by newest version number. This way you'll see which packages belong together in this and can mark those installed on your system for upgrading.
Those you need are newest version number
2.24.25-1 (look for libgtk2.0-0 and other packages with identical install version number; for the gtk2-programs) and
3.14.3-1 (look for libgtk-3-0 and other packages with identical install version number; for gtk3-programs).

Edit: Third alternative: you could downgrade several packages starting with libglib2.0- to version 2.41.1-2 or before (to be got from snapshot.debian.org if you haven't got them in /var/cache/apt/archives anymore). This of course won't work if you installed other packages from testing which depend on a higher version.
Tower: Sparky 64 bit Mate+mintmenu - Netbook: Sparky 32 bit Mate+mintmenu
alobo
Level 1
Level 1
Posts: 38
Joined: Sun Jun 17, 2012 3:17 am

Re: mintupdate: Attempt to unlock mutex that was not locked

Post by alobo »

Solved by following alternative 2.
Thanks!
ljdellar
Level 1
Level 1
Posts: 5
Joined: Tue Apr 08, 2014 8:04 pm

Re: mintupdate: Attempt to unlock mutex that was not locked

Post by ljdellar »

I found a fix someone else posted, but cannot remember who or where, but it involves two new lines in mintUpdate.py

Open a terminal and do

Code: Select all

    sudo leafpad /usr/lib/linuxmint/mintUpdate/mintUpdate.py

Find the following...

Code: Select all

        auto_refresh = AutomaticRefreshThread(treeview_update, statusIcon, wTree)
        auto_refresh.start()
        gtk.main()

and edit it so that you have

Code: Select all

        auto_refresh = AutomaticRefreshThread(treeview_update, statusIcon, wTree)
        auto_refresh.start()

        gtk.gdk.threads_enter()
        gtk.main()
        gtk.gdk.threads_leave()

Save and do an apt-get update, then run mintUpdate again.

Worked for me.

If anyone knows who it was who came up with this please credit them!

LJ
Locked

Return to “LMDE Archive”