When trying to select items in Revelation [http://oss.codepoet.no/revelation/] tree pane, an error dialog appers. See bug reports: https://launchpad.net/distros/ubuntu/+source/revelation/+bug/56744 http://oss.codepoet.no/bugzilla/show_bug.cgi?id=180 Upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=347273
Created attachment 97460 [details, diff] pygtk-2.10.1-iter-fix.patch Fix taken from gnome-cvs
Created attachment 97461 [details, diff] pygtk-2.10.1-r1.ebuild.patch Ebuild patch
The above patches work for me. Hope that helps someone.
Fixed in 2.10.1-r1
This fix makes deskbar-applet and gajim dump core here. *** glibc detected *** gajim: free(): invalid pointer: 0x3283156c ***======= Backtrace: =========/lib/libc.so.6 [0xfdd564c]/lib/libc.so.6(__libc_free+0xc0) [0xfdd70e0]/usr/lib/libglib-2.0.so.0(g_free+0x54) [0xf79f7c4]/usr/lib/libgtk-x11-2.0.so.0(gtk_tree_iter_free+0x2c) [0xe579e4]/usr/lib/libgobject-2.0.so.0(g_boxed_free+0x168) ... I'm back in 2.10.1, where I have not yet found a problem. I'd reconsider the patch.
Same problem with crash from deskbar applet on amd64, back to 2.10.1
I've filed a separate deskbar/pygtk bug as bug 149893, since this one is marked as fixed.
This fix breaks other apps. Reopening since this isn't a "fix"
Fine. I've masked the fix.
Sorry Guys. Have not thought of this consequences. As a result the fixed bug from the gnome bugtracker should be reopened. As shown here their fix does not seem to work in the wild. I like to apologize for not testing this fix in depth. I simply put my trust in the Gnome folks. Will not make this mistake again.
The patch that we used, and which made it into pygtk-2.10.2 was apparently having some minor reference counting issue, causing big problems. pygtk-2.10.3 should remedy the fallout. I have added 2.10.3 to the tree now (sorry it took a while to get there), and would appreciate if it would be tested if this fixes all the issues that were happening wrt this bug report here
works for me
I have now removed the broken 2.10.1 versions from the tree. As there have been no failure reports, I'm closing this as fixed again