debian bug #762870Brian49 wrote:An upgrade to initramfs-tools has just come through, from 0.116 to 0.117. The upgrade seemed to go smoothly, but it made my system unbootable - various critical files couldn't be found. I had to restore my system from a backup.
LMDE Breakages (Tracking SID)
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Re: LMDE Breakages (Tracking SID)
Re: LMDE Breakages (Tracking SID)
The glitch in initramfs-tools appears to have been fixed in v.0.118.
Re: LMDE Breakages (Tracking SID)
Thanks Brian...
Have not been d-u for a while.
Today d-u... 650 over packages to upgrade, ended up fully d-u, no issue on reboot and running..
Have not been d-u for a while.
Today d-u... 650 over packages to upgrade, ended up fully d-u, no issue on reboot and running..
Re:Attempt to unlock mutex that was not locked - FIXED
Hi wayne....
Todays update to GLlib fixes many gtk issues.
Gdevilspie (among many others.. ..) is working again...
Todays update to GLlib fixes many gtk issues.
Code: Select all
gene@sparky:~$ apt-cache policy libgtk2.0-0
libgtk2.0-0:
Installed: 2.24.25-1
Candidate: 2.24.25-1
Version table:
*** 2.24.25-1 0
500 http://http.us.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
2.24.24-1 0
500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
http://forums.debian.net/viewtopic.php?f=6&t=117788Attempt to unlock mutex that was not locked
Postby sjukfan » 2014-10-02 08:42
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.
Gdevilspie (among many others.. ..) is working again...
Re: LMDE Breakages (Tracking SID)
Which repos do I need to get the 2.24.25-1 versions?
I just get 2.24.22-1 in my Synaptic
(using LMDE MATE)
Thanks
Agus
I just get 2.24.22-1 in my Synaptic
(using LMDE MATE)
Thanks
Agus
Re: LMDE Breakages (Tracking SID)
Hi Agus..
This thread is for folks tracking Debian SID. If your on the default LMDE repos, you need to wait for them to fix it. But to answer your question its from Debian SID..(unstable). I would not recommend getting it alone from SID unless you feel experimental and have a recent backup.. Things can happen... (Especially with LMDE being so OLD.. What... going on 8-9 months without an UP..?..)
See OP to clarify... http://forums.linuxmint.com/viewtopic.p ... 8&t=133211
This thread is for folks tracking Debian SID. If your on the default LMDE repos, you need to wait for them to fix it. But to answer your question its from Debian SID..(unstable). I would not recommend getting it alone from SID unless you feel experimental and have a recent backup.. Things can happen... (Especially with LMDE being so OLD.. What... going on 8-9 months without an UP..?..)
See OP to clarify... http://forums.linuxmint.com/viewtopic.p ... 8&t=133211
Code: Select all
Version table:
*** 2.24.25-1 0
500 http://http.us.debian.org/debian/ unstable/main amd64 Packages
Re: LMDE Breakages (Tracking SID)
@alobo: I see that you're troubled with the 'mutex' issue. there are several alternative to fix that problem but downgrade the package is probably the safest option for you. no one know what will happened if you try grab something from testing (or even sid).