GNOME Bugzilla – Bug 359231
validate_visible_area() sometimes passes mismatches (tree,node)/(iter,path) to validate_row
Last modified: 2007-02-18 22:38:51 UTC
After connecting to my jabber server my contacts are displayed. Sometimes a avatar images is note shown with the correct size after connected. I have to click the group of this contact, reopen it with click again and the avatar image size is correct.
Created attachment 73927 [details] This animated GIF will hopefully help to understand my problem :)
Yea, I've seen this too, and tried to fix it without success :/
This is a GtkTreeView bug I think. It only ever occurs for the first contact in the first group with an avatar for me. Not sure if it is the same for everyone else? I think GAIM have had the same problem too.
I can confirm that gaim has the same problem. It seems to be a GTK bug.
I've seen it sometimes in gaim too; but this is going to be difficult to fix if it isn't easy to reproduce.
It happens every time I start gossip so it should be fairly easy to reproduce. I would just check in gossip first since we done some weird things in our cellrenderer.
Reassigning
Old summary: Resize of the avatar image after connecting
Created attachment 74884 [details] [review] fix? I managed to reproduce this in gaim, but not in gossip (it depends on some stuff it looks like). This patch fixes the problem for me. Could some of you try if this fixes the issues? (fixing this was evil btw)
The patch works for me with Gossip, I can easily reproduce the bug without the patch and not been able to do it with the patch. Great work Kris!
Committed on HEAD and gtk-2-10.
*** Bug 409169 has been marked as a duplicate of this bug. ***
I'm using the GTK package 2.10.9-ubuntu1 in Ubuntu Feisty and I'm still seeing the problem in Bug 409169, which either indicates that either the bug isn't fixed in this release, or that it wasn't the same problem. I'm just bringing this up because the fix was apparently committed four months ago, so I'm just checking...
Fix should be in 2.10.7, and we haven't seen any instances of this problem ever since ...