Comment 24 for bug 391398

> Kim: Deprecated API is only removed when 3.0 is released, not in releases leading up to 3.

This is an *development* release leading to 3.0. From my understanding deprecation is done in two steps.
1) Deprecate only the header, not the code. This way new programs don't use the old function and old programs can still be compiled without GTK_DISABLE_DEPRECATED. Incidentally, gtk itself is compiled (always for an development branch) with GTK_DISABLE_DEPRECATED in order to spot deprecated code paths and not use them internally. This is what is done in 2.17.x I believe.

2) Removal of deprecated code. Old program using the deprecated function won't compile anymore. This will happen in the unstable leading to 3.0 (perhaps 2.19.x ?).

So to sum up. GTK *internally* was still using a depreacted function in 2.17.2 despite compiling with GTK_DISABLE_DEPRECATED, hence the segfaults. Bummer, developpment releases are precisely done for this puropose, testing new features and bug reporting. No one should complain about this. The bug was fixed upstream even before this bugreport was filled. The package is lagging a bit behind but considering the huge change that 2.17.3 is (integration of the client-side-window branch in particular, which breaks the directfb port and still has a few rendering glitches), one can hardly blame the debian/ubuntu package maintainers for not uploading this version yet.

I have tested the three patches against the current 2.17.2 in karmic. I have uploaded the patched packages in a ppa I just opened, they are queued for building and should be ready sometime today.

>If it is the latter the GTK+ maintainers are smoking crack and someone probably needs to hit them with a cluebat.

This is a bugtracker, not a forum, please refrain from doing such comments, it only add to the noise.
Everyone is welcome to try the new packages when they are built:

https://launchpad.net/~kim.nguyen/+archive/ppa