On Thu, Jun 30, 2011 at 10:16 AM, LucaDC <email@example.com> wrote:
Mmmh, actually I rely on the devlibs repository for all updates of such
Josh Andler wrote:
> It seems likely that it may have to do with something that has changed
> GTK somewhere between what we had before and the version we have now. The
> only way I can think to test/check where things went wrong is to download
> other GTK binaries between what we had before and what we have now until
> find one that doesn't show the issues and work up from there until you can
> identify when it broke.
I can see that in rev.22 there has been an update to GTK 2.22 and Glib 2.26.
The preceding one was in January (update to Cairo 1.10.2) and I feel that
the problem was not present so far ago.
The rev.22 update has been quite massive so I don't think I'll be able to
make small steps back.