I guess it's too late to update gtk-vnc at this point. RC is this Friday and final release next Thursday...
We already have vinagre 0.5.1, and that patch is only for debugging purposes? If so, it's not probably worth the risk at this point (without looking at the diff, svn.gnome.org isn't working well for me...).
Can't we backport a fix for this bug from the gtk-vnc hg repo?
Will gtk-vnc 0.3.5 fix this bug?
Soren, what's your opinion on updating gtk-vnc?
Jonh,
I guess it's too late to update gtk-vnc at this point. RC is this Friday and final release next Thursday...
We already have vinagre 0.5.1, and that patch is only for debugging purposes? If so, it's not probably worth the risk at this point (without looking at the diff, svn.gnome.org isn't working well for me...).
Can't we backport a fix for this bug from the gtk-vnc hg repo?
Will gtk-vnc 0.3.5 fix this bug?
Soren, what's your opinion on updating gtk-vnc?