Comment 46 for bug 247376

Is there someone with indepth technical knowledge of X.Org here, who could report the exact problem, and make suggestions to ATI?

This is a very critical bug for many users, so I really hope it can be fixed before Intrepid is becoming stable.

I don't think this ticket should be closed: When a working fglrx driver is not available before the release of Intrepid, then we need to do discuss how we handle this. We cannot just let X break for all the fglrx users. So I think we should leave this bug open to discuss a "solution". Like the one suggested by Michael Vogt in comment #25 of this bug: "Should update-manager (on release upgrades) auto warn people using the fglrx driver not to upgrade (yet)? Or should it auto transition them to either ati or vesa ?"