exaile crashes on startup (threads_init)

Bug #1014484 reported by rpointel on 2012-06-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Dustin Spicuzza

Bug Description

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 version).

Related branches

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!

Changed in exaile:
assignee: nobody → Dustin Spicuzza (dustin-virtualroadside)
importance: Undecided → High
status: New → Incomplete
milestone: none →

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

Changed in exaile:
status: Incomplete → Fix Committed
Changed in exaile:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers