Issue #220 resolved

crashed with "Attempt to unlock mutex that was not locked"

Anonymous created an issue

ubuntu utopic system

after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop). the crash appears to be gtk2/pygtk related: in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270 is a call to GDK_THREADS_LEAVE

if (g_main_loop_is_running (main_loops->data))     {       GDK_THREADS_LEAVE ();

which in turn triggers a call to g_mutex_unlock_slowpath. it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's a check now on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").

so, many superfluous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case

workaround: commenting the line 185 into that file does the trick. (gtk.gdk.threads_init() )

( sudo gedit /usr/lib/python2.7/dist-packages/radiotray/SysTray.py )

https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564

Comments (6)

  1. Log in to comment