Hi there Leann, Unfortunately I was not there 4 hours ago to immediately answer your question.
Anyway, I ran dpkg-reconfigure -au as this will make the dpkg- reconfigure command remember the last configuration. If you thereafter run dpkg-reconfigure -p low debconf and set it to readline + priority low, and then again run dpkg-reconfigure -au, you will be able to just click enter for packages that you do not know, and therefore not wish to reconfigure. You may want to do this when trying to reset system settings, for which you do not know the responsible package. In theory this approach should work fine, as the default package settings should be identical as those set during the initial install. If not, then I would personally expect any deviations to be documented somewhere centralized, perhaps dpkg-docs? Is it correct that you can do a fresh jaunty install and restore some packages through aptoncd restore, run update-manager, and then find that the dpkg-reconfigure defaults are different from your actual packages configurations (e.g. by running dpkg-reconfigure -ap critical)? I find that quite bizarre. I certainly did not deliberately change any package configurations. Either way, this does not mean I necessarily disagree though with your decision o label this as won't fix, as you may have other priorities. It is maybe worth considering still to verify if there is a kernel and/or xorg incompatibility with a proprietary driver or the BIOS though, what I suspect actually. (maybe similar to (?): https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- evdev/+bug/323694) Thanks, Thomas -- jaunty kernel 2.6.28-11.38 does not boot, neither does the latest kernel from the git repo https://bugs.launchpad.net/bugs/354532 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
