Comment 8 for bug 178656

I'd say this isn't quite a duplicate. Unless xrandr is relying on gtk for some reason, this is a different issue and should either be considered not a bug or just something that won't be fixed at the worst, and hopefully fixed at best. If this would infact be a bug in itself and related to bug #245383 without the problem in this case being in gtk, then the problem in gtk would be invalid as simply a workaround of a problem actually in the ati drivers or the xserver and just exposed by gtk.