Comment 57 for bug 31830

Revision history for this message
Bryce Harrington (bryce) wrote :

This is long since fixed in X. Resolution handling has been completely revamped since this bug was first reported.

The original issue was just that for some monitors it used to be that you had to manually specify H/V rates in order for the X to work because the install-time config generator wasn't able to detect that properly. But today those scripts are eliminated, and now X does all the resolution detection internally, which works like 99% of the time. (There are cases where it still fails, see https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/194760 as the main example, but these are rare corner cases now.)

Ricardo's last comment was in early 2007 which iirc was before much of this new stuff hit. I'm going to go ahead and make a guess that with the new resolution autodetection code, his problem went away, and will close the bug.

Other commenters on this bug have indicated their issues were solved by this change. Anyone else still having resolution detection problems - please report as a new bug, don't re-open this one.