The issue was introduced by the fix for the bug: https://bugzilla.gnome.org/show_bug.cgi?id=736125
i.e. commit: https://git.gnome.org/browse/gtk+/commit/?id=c55ff6e41fb3c6272b5e7a084c8273dea60d7dee I've reverted the commit from Matthias, since it broke the build, and I'd also revert the commit from John Ralls, because it introduced a regression: now everything that creates a class with a key binding requires an open display connection — including building the GTK API reference. This is not really something that can be fixed with a GOnce, though; installing key bindings happen in the class initialization all over the place. We could have something that defers the initialization of the actual key binding until the widget is realized, i.e. when we know it has a display connection available. Ciao, Emmanuele. On 29 August 2015 at 14:01, Colin Walters <walt...@verbum.org> wrote: > In > https://git.gnome.org/browse/gtk+/commit/?id=6838861d26bfec9af53438022bd1f5b60bab3bf4 > > I think we need to avoid get_type() functions requiring any explicit > initialization or external resources; we definitely don't want to require an > X server for builds that use introspection. > > See: https://bugzilla.gnome.org/show_bug.cgi?id=696457 for an earlier > variant. A general pattern here is to break out initialization components > into GOnce. > > Right? > _______________________________________________ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gtk-devel-list -- https://www.bassi.io [@] ebassi [@gmail.com] _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
