Created attachment 414338 [details, diff] fixed problem 1), tested with imap 1)"Attempt to unlock mutex that was not locked" only happens with non-file mailbox, for me with imap. this bug didn't occur with gnubiff compiled against gnome-panel since gnome2 has for compatibility reasons allowed unlocking a mutex twice. gnome3 doesn't. 2)additionally there is a strange bug which disallows configuration-file ~/.gnubiffrc to be read by default: "WARNING **: Configuration file () not found!" and adding the commandline-option "-c filename" doesn't help either. that's probably also related to getting rid of gnome-panel, since same version had no such problems before... attached an epatch_user fix for 1), although upstream probably should try to fix it by adding a lock before the unlock so that future changes to this destructor wont forget it.
when I try saving the config I get: Gtk-CRITICAL **: gtk_list_store_get_path: assertion 'iter->stamp == priv->stamp' failed any idea what that means?
In https://projects.archlinux.org/svntogit/community.git/tree/trunk/mutex.patch?h=packages/gnubiff there is a similar patch that also solves the problem 1 (which I am using now). Regarding the problem 2, it has not happened to me, could be due to the USE flags? In my case I have activated fam, nls and password. Perhaps one of the following patches can help correct the bug: https://sourceforge.net/p/gnubiff/bugs/60/ https://sourceforge.net/p/gnubiff/bugs/58/
