If you have an opportunity there are some things you might want to try with the new glib. I don't see an obvious bug in the code besides the possibility of an optimization being done because a memory location is volatile but isn't marked as such. The first thing to try is building from source and doing so without optimizations CFLAGS="-O0" . Does the problem exist?
I'd then like to know the output with it configured with CFLAGS="-DDEBUG_MULTITHREADED" . This will display additional text to the console that might help me out. Although you have marked the bug as invalid, I have an interest in these last couple tests so I can check our code. It is possible in the future that Ubuntu will use a newer glib and we'll be revisiting this issue again. That is of course if there isn't a bug on the glib side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346567 Title: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1346567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
