This bug appeared again on 2011-04-12 which didn't exist on my machine before. It probably appeared after an X server upgrade.