3. you aren't providing the right infos to the devs, and if they'd want to try simulating the bug they'd have some difficulties in it and they'd have a very harder time in fixing the eventual issue. when posting a bug you should first ascertain where it's the right place to post it (it's still not clear if this is an fglrx bug since it works on a very similar system without issues - mine and also there are reports of another x200m working well also in the 7.2 thread), then you should ascertain that it's really a bug and not a configuration problem due to something on your system (it may be everything), then you must post your xorg.conf (without which the devs wouldn't konw where to start fixing the bug), your Xorg.0.log, the dmesg and eventual logs of the app crashing. if you don't know where to get that infos then ask for help.
last, but not least, the main bugzilla page is down to bug reports posted in this way. i'm quite sure that devs are tired of people who continue to post there bugs with not enough infos or without having first ascertained if the bug posted is really a bug or not, or of bug reports reported as major when in fact they aren't major. i really think that the bugzilla would be forbidden to normal users. they should have a forum where to post problems, and the forum admins, after verifying that the problems reported are really bug would post them in the right way on the bugzilla. here on phoronix i've seen more than one capable person and i think that they'd all agree on what i'm saying. maybe the problem with the fglrx developing is in a minor issue due to some of this misreported bug reports.