LinuxBBQ

2014/10/02: Do not upgrade to the newest libglib2.0-0 but I think it could be already too late, so you have to keep the pieces. ;) I won't bother to install the older version, no fucks given.

That happens when you try to use the damn UI once. Sonata and Deadbeed crash after opening them with a similar message at the end. I am not sure if it is upgrade related but I think so because they worked before.
Wtf?

Edit: Do not upgrade to the newest Gtk if you rely on some apps that use this freaking toolkit that should finally die!

This sounds equal:

https://bugs.debian.org/cgi-bin/bugrepo ... bug=758619

It has to be shitty Gtk like always. Reportbug, the UI, works neither. Good that I use the terminal for this otherwise how to report bugs Debian? On the other hand no one is reading them in months.

Edit: And now I found the culprit, indeed Gtk, version 3.13 (beta quality of course). So, that should be in upgrade warnings.

https://www.mail-archive.com/debian-bug ... 59116.html

The friends over at Siduction already knew a shitstorm was coming but this time I could not read them because their site was unreachable this evening for me.

http://forum.siduction.org/index.php?topic=4963.0

Thanks for the warning!

libgtk 3.14 behaves the same.

Unbelievable...

David, what if the default theme is switched to something like clearlooks-phenix or so?

I tried it with different themes, Clearlooks Phenix/Adwaita (the new shit), still nothing and it is funny because Sonata is a Gtk2 app and Deadbeef should be, too, unless you tell it otherwise.

Edit: No matter what I do, cannot fix this mess right now. I tried also with pure Gtk2 themes, no dice.

I can confirm this shittiness when running (some) gtk2 apps on antiX eg spacefm gives the mutex error but gftp doesn't.

Thanks for confirming.

Let us see what apps that are. Sonata is python, so is Reportbug IIRC but what the fuck has Deadbeef to do with python and then Wicd works and is written in python? Maybe I saw something pygtk related.

Thanks david for testing the other themes and antix for confirming. The only package that these crashing apps have in common is:

libglib2.0-0

This does not necessarily mean all rdepends of libglib2.0-0 will crash, but probably those that call a certain routine (mutex or what the fuck). So yeah, the first bug report posted above is the one to follow, I am not sure if gtk3 is really the one to blame (but probably something they implemented there that is not backward compatible)

we cannot really fix all the wrong code everywhere

https://mail.gnome.org/archives/commits ... 08240.html

Edit: Bacon is right, the affected package seems to be libglib2.0-0 and the idiots migrated the issue already to Testing.

one word: wow!

siduction/fixes had this one:
2.37.5+really2.36.4-0r0

seems the package has been problematic for quite some time, if we see the version number at which siduction placed the fix. Unfortunately fixes gets skipped as soon as newer packages are in the main repos.

gtk guys wrote:we cannot really fix all the wrong code everywhere

Comedy gold. :D

Fixed with libgtk2.0-0 version 2.24.25-1.