From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021203
Description of problem:
Kudzu does not appear to detect changes in monitors between reboots.
Steps to Reproduce:
1. Use a Red Hat Linux 8 machine with a given monitor
2. Turn off computer and connect a new monitor to the same PC (preferably a
monitor that doesn't support the same res/refresh as the monitor from step 1 to
demonstrate how scary this is for the user)
3. Turn on computer again
4. Watch the new monitor choke on the new res/refresh rate
Actual Results: X did not come up because the new monitor doesn't handle the
configured resolution of the old monitor
Expected Results: kudzu should detect the new monitor and prompt to configure X
This effectively breaks X, so I've set it to "High" for severity - I hope this
Currently, the DDC monitor probe is only done on-demand by config tools, as it
has caused strange behavior in the past on some graphics chipsets. So, it's not
actually run during the boot time probe.
Bleh... well, would a "probe by default unless the chipset appears on this
blacklist" system be possible, or is that still too dangerous?
Realistically, where it has fallen down seems related almost as much to BIOS as
it does chipset. Which makes this impractical.
The long-term solution is to have the X driver automatically adjust to monitor
changes; that is where progress will be made. Until then, it's unlikely that the
behavior in kudzu will change. Therefore, closing this bug.