On Mon, Jan 28, 2008 at 11:14:19AM -0500, Bill Meier wrote:
> Ulf Lamping wrote:
> > This seems to be a bug in the GTK libraries, we should simply "go back"
> > to the old GTK version that works and put some pressure on the GTK guys
> > (the bug report seems to be written already).
>
> Bottom Line:
>
> I now think the right answer is to follow Ulf's suggestion to fall back
> to the GTK version currently being used with 0.99.7 and to push to get
> the GTK problem fixed (or a work-around determined).
+1 for me
Can someone bump the GTK version back to GTK+ 2.12.1 with GLib 2.14.3
which seems to be the last combination on windows that doesn't have
this problem?
Cheers,
Sake