Thanks for the patch. I must admit I'm not too familiar with GtkBuilder and I'm a bit concerned that the patch as is might prefer an autogenerated "ID" from GtkBuilder over a name that had been explicitly set in the application code. But I might be on the wrong trail entirely here...
It would help to know what names you're getting out of GtkBuilder here. Did you create them yourself in the xml file or did GtkBuilder generate them somehow? Also PyGtk, Gtk+ versions would be useful.
From a brief google, I think the fix for this bug is the trigger here
Thanks for the patch. I must admit I'm not too familiar with GtkBuilder and I'm a bit concerned that the patch as is might prefer an autogenerated "ID" from GtkBuilder over a name that had been explicitly set in the application code. But I might be on the wrong trail entirely here...
It would help to know what names you're getting out of GtkBuilder here. Did you create them yourself in the xml file or did GtkBuilder generate them somehow? Also PyGtk, Gtk+ versions would be useful.
From a brief google, I think the fix for this bug is the trigger here
https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 591085
which has also caused a mild panic in a few other applications e.g. see here
https:/ /bugs.launchpad .net/ubuntu/ +source/ pygtk/+ bug/507739