exaile crashes on startup (threads_init)

[rpointel]

On OpenBSD, the default mutex type is PTHREAD_MUTEX_STRICT_NP (and not PTHREAD_MUTEX_NORMAL), means that unlocking an unitialized mutex will end up in a segfault or abort.
In the past, glib didn't care about it but recent versions now catch this error.
In effect that means exaile crashes right when starting... It is due to missing threads_enter / threads_exit calls.
See http://www.pygtk.org/docs/pygtk/gdk-functions.html#function-gdk--threads-enter for details.

Attached patch fix the issue for me (for 0.3.2.2 version).

[Dustin Spicuzza (dustin-virtualroadside)]

Can you try the version of exaile in bzr -- the code has changed quite a bit. I don't have OpenBSD, but I'll put the fix in my branch (which will eventually get merged into main again) if you can give me a patch for trunk. Thanks!

[rpointel (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcv-launchpad-a811i2i3ytqlsztthjth0svbccw8inm65tmkqp9sarr553jq53in4xm1m8wn3o4rlwaer06ogwvqwv9mrqoku2x334n7di44o65qze67n1wneepmid)]

Hi,

exaile does not work directly, I need this patch with the development version.

Is it ok for you?

Remi.

[Dustin Spicuzza (dustin-virtualroadside)]

I see that gajim uses this same fix. It doesn't break my system, so I'll push it for you. Thanks for the patch!

Pushed in revision 3971