interim_descriptor wrote:
> I don't know what the process for this is, but somebody in Ubuntu should
> really consider pushing this fix into a Hardy Heron update.
I opened bug 218667 for updating gtk-vnc for Hardy, but it was too late and it
introduced some regressions so this won't probably hit hardy-updates
unfortunately. Unless we can backport a non-intrusive patch for them, without
updating gtk-vnc entirely.
interim_descriptor wrote:
> I don't know what the process for this is, but somebody in Ubuntu should
> really consider pushing this fix into a Hardy Heron update.
I opened bug 218667 for updating gtk-vnc for Hardy, but it was too late and it
introduced some regressions so this won't probably hit hardy-updates
unfortunately. Unless we can backport a non-intrusive patch for them, without
updating gtk-vnc entirely.