Comment 4 for bug 430203

> so is this a metacity issue?

This is most definitely a metacity issue. The rate limiting does not occur in compiz, nor does it occur in a simple xterm session.

> does applying the upstream patch fixes the issue for you?

Dunno. Is there an easy way to do this? I tried apt-getting the source, making the change by hand, and building, using the Ubuntu Wiki's PackageUpdate guide. But on `debuild -S -sa`, I get an error, the relevant portion of which seems to be:

debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or directory
debian/rules:4: /usr/share/cdbs/1/rules/simple-patchsys.mk: No such file or directory
debian/rules:5: /usr/share/cdbs/1/class/gnome.mk: No such file or directory
debian/rules:6: /usr/share/cdbs/1/rules/utils.mk: No such file or directory
debian/rules:7: /usr/share/gnome-pkg-tools/1/rules/uploaders.mk: No such file or directory
debian/rules:8: /usr/share/gnome-pkg-tools/1/rules/gnome-version.mk: No such file or directory
make: *** No rule to make target `/usr/share/gnome-pkg-tools/1/rules/gnome-version.mk'. Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
debuild: fatal error at line 1334:
dpkg-buildpackage -rfakeroot -d -us -uc -S -sa failed

Given that I don't know what debuild is trying to do to begin with, I have no idea how to fix this. But given that (1) the bug only reveals itself under metacity, (2) the bug has been reported and fixed on the metacity bug tracker, and (3) the fix is both simple and not present in the Karmic source, I think it's fairly clear that this is the problem.