No, it's not a debconf bug either; debconf is just doing what it's told to do.
x11-common's config script asks x11-common/xwrapper/nice_value at priority low, and then if validation fails it asks x11-common/xwrapper/nice_value/error at priority critical and goes round the loop again. Firstly, if the user never saw the question in the first place (and the previously stored value is wrong for some reason), this is bizarre UI; secondly, it never bumps the priority after error so the user never gets an opportunity to enter a new value (although it does set a safe value, so it's probably just poor UI rather than an infinite loop). I imagine that the xorg maintainers will have further questions to try to work out how things got into this state, though. ** Changed in: debconf (Ubuntu) Sourcepackagename: debconf => xorg -- adept ask a question but not possible to answer https://launchpad.net/bugs/41976 -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
