On Monday 28 July 2008, Jérémy Bobbio wrote: > > The following sequence (at medium priority) will result in an > > apparent loop: > > 1 Allow root -> yes > > 2 Root password -> empty > > 3 Confirm passwd -> empty > > 4 Error dialog -> continue > > 5 Back to 1: Allow root -> go back > > > > This should result in the menu being displayed, but does result in a > > loop: > > 4 Error dialog -> continue > > 5 Back to 1: Allow root -> go back > > > > It's possible to break out of the loop by using go back instead of > > continue, but that's not obvious. > > > > This may well be a cdebconf error instead of an error in user-setup. > > Possibly the queue is not cleared correctly/completely. > > A cdebconf trace is probably needed here. > > debconf receives: > INPUT critical user-setup/password-empty > INPUT low passwd/shadow > INPUT medium passwd/root-login > GO > > So actually, the behaviour of the "Go back" button is right for the > newt frontend according to the questions asked.
This analysis looks incomplete to me and the part you show here is out of context, so impossible to draw conclusions from. I still don't see how this explains why you'd get the error dialog displayed *again* after choosing <go back> from the "Allow root" question. And I also still don't see if this is a state machine error or a cdebconf issue. An attachment with the full syslog including 'set -x' output *and* debconf debugging, or at least for the relevant part from the start of user-setup would have been helpful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]