Comment 13 for bug 29540

Revision history for this message
Peter Schwenke (bluetoad) wrote :

I spent some time looking at this and following the config script for Dapper and Breezy.

I ran it with DEBUG_XORG_DEBCONF=1 and DEBCONF_DEBUG="developer"

It is detecting the ranges but not writing them out

debconf (developer): <-- GET xserver-xorg/config/monitor/horiz-sync
debconf (developer): --> 0 28-80
debconf (developer): <-- GET xserver-xorg/config/monitor/vert-refresh
debconf (developer): --> 0 43-60
debconf (developer): <-- GET xserver-xorg/config/monitor/use_sync_ranges
debconf (developer): --> 0

I suspect this is because xserver-xorg/config/monitor/use_sync_ranges

is off. It is on in Breezy. I read somewhere that xserver-xorg/config/monitor/use_sync_ranges controls whether the sync ranges are written to the config file.

However, that setting would be off on all boxes.... Admitedly, I have only tried The Dapper flights on the A22p.

I haven't worked the preseeding out yet (if there is a way of doing it without building up a CD image).

I'll attach the log of the reconfigure and the debconf-show.