Comment 242 for bug 160311

I thought I was the only one who really had a problem with this. But then I thought that wouldn't make sense, and that probably nobody had filed a bug.

So I searched and found this.

And I'm shocked this HUGE bug has been filed here for around 3 years yet it's low priority.
How can this be low priority if it affects _every_ window? And this is ubuntu, not some distro targeting command-line hackers.

I'm sorry I can't contribute any code to fix it, but I think you should reconsider some of your priorities.

Now, from looking at http://blogs.fedoraproject.org/wp/mclasen/2010/10/09/getting-a-grip/, GTK+3 will include this (hopefully this is mainstream and not only Fedora), but unless GTK+3 is included in natty (AFAIK it is, correct me if I'm wrong. and I hope I'm not… also, this leaves lucid out in the cold, and the latest LTS shouldn't be left suffering this terrible bug) and all existing GTK+2 applications use GTK+3 when ran on a system with GTK+3 (which I doubt, considering how horrendus GTK+1 apps look) the outcome won't be pretty at all...