This bug disappeared after I updated to the 8.3 fglrx driver using EnvyNG. I don't know whether it was a bug in the earlier drivers or an incorrect configuration setting that EnvyNG got right.
This bug disappeared after I updated to the 8.3 fglrx driver using EnvyNG. I don't know whether it was a bug in the earlier drivers or an incorrect configuration setting that EnvyNG got right.