This seems to be due to a behavior change in GTK+ 3.x. The exact same code displays fine on GTK 2.x, but results in this issue under GTK+ 3.x.
This seems to be due to a behavior change in GTK+ 3.x. The exact same code displays fine on GTK 2.x, but results in this issue under GTK+ 3.x.