Looks good, this is certainly an improvement over the "X broke, you are
to keep the pieces" dialog.
I would suggest several other things:
- when I set the driver to "iwantaponny" (or physically change the
card) I would like the tool to automatically remove the card section and
generate a new one, and only bug me if X fails to start after that.
- an option (default on) to save screen data, and reuse it when screen is not
detected. This could be done as a gdm (or similar) script once X starts. To
avoid the need to start in some sort of VGA failsafe mode in most cases this
could have several modes
1) detection working (and used by the driver, some have it off by default) -
all OK, save data
- if the monitor is not in a database of known monitors, offer the
option to send the data somewhere for inclusion. The user should fill in the
manufacturer and model because the DDC data often says something else. This
probably should be the default only in beta distributions. When sent, the
monitor should be added to the local database or some whitelist so that the
script does not ask again. Perhaps the script could even ask if the
manufacturer/model in the database and the detected parameters are correct.
2) detection not working, saved data present - offer the option to use the
saved data
- once X is restarted ask to make the monitor data default regardless
of autodetection - should be hard to select when the screen is not working
3) detection not working - offer a selection of monitors to choose from +
some generic types like 19" LCD (1280x1024) or 17" CRT (1024x768)
- on restart the same as 2)
Note that many monitors that can be detected on one card would fail on
another, and some cards may be completely broken in this regard. Thus
the semi-automatic building of monitor database could be helpful, and
monitors that report bad data could be singled out - users can send the
saved data when stuff breaks.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
