Sourcery - Attempt to unlock mutex that was not locked

[Ali82]

gtk.gdk.threads_init()

No, that is not the problem. That is a perfectly valid call. If it doesn't work, your system is broken.

.

I do agree with you, something is locally broken, but my system is not, because it is intact (see below).

I'm building local versions keeping the system versions intact (LD_LIBRARY_PATH ?)

To me, that reads like "I have no idea what I'm doing and I'm playing around to see what will break".

.

Really? What if the applications that you are developing depends on API that was introduced in gtk3.14? And you want to stick with your current system setup. The only way is to compile gtk3.14 with its dependencies in your home folder and develop/link your application against it. I don't want to update the whole system or change my system to a distro that has gtk3 > 3.14 by default now. What I did don't not break anything, the sourcery issue was noticed because I started it using the terminal that had the env variables pointing to the home local versions of glib2. Otherwise, it is runs perfectly fine. I repeat, I know what I'm doing and I do not alter salix's defaults installation. It is my main workspace machine.

Again, this is not a problem in sourcery or a problem with glib 2.42 itself. Sourcery works just fine without any changes under slackware-current, which uses glib 2.42.

You are right, it works under slackware current. I think I know now what the problem is, slackware current has gtk 2.24.29, while 14.1 has gtk 2.24.20. Combining, always locally, glib-2.42+gtk2.24.20+pygtk and sourcery runs perfectly fine when launched against those versions. Must be a incompatibility bug that got fixed in gtk2. Of course it is not my goal to run sourcery like that, I just wanted to have gtk3.14 locally in salix, until the next version gets released.

Feel free to do anything you like. Statements like yours make me feel that I should reconsider responding to any future issues you might have. After all I don't really understand anything and you know better.

Please don't take it personal. I do appreciate your help and quick replies. I understand that obviously you cannot give support/help for altered installations. It is my mistake that I did not test on slackware current first, otherwise I would have got the gtk 2.24.29 thing immediately without opening this thread.

Thanks.