With regard to your ubiquity change, I think I'd rather have ubiquity check passwd/allow-password-empty and continue to disable the next button for empty password/verified-password entry boxes if it's false; I don't think this should be too difficult. My reasoning is:
* If you don't know about the allow-password-empty change, it's a bit of a weird UI change. * It's better to handle problems as early as possible rather than having to go through user-setup and back. Out of necessity, there are some problems that we can only deal with by the latter method, but where it's feasible we should prefer to simply prevent the user from going forward until they've filled in the necessary information. -- Cannot install with a blank password https://bugs.launchpad.net/bugs/280014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
