** Changed in: installation-guide (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/280014
Title:
Cannot install with a blank password
To manage
** Changed in: user-setup (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/280014
Title:
Cannot install with a blank password
To manage notifications about
** Branch linked: lp:ubuntu/ubiquity
--
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
** Changed in: installation-guide (Ubuntu)
Status: In Progress = Won't Fix
--
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
I'm marking the installation-guide change won't fix, have closed the
Debian bugs (or attempted to do so), and intend to revert this as part
of bug #347207. There are other ways to achieve the goal (which isn't a
very good goal anyway), and it's easier to stay in line with trunk.
--
Cannot
For the record, I renamed this to user-setup/allow-password-empty for
consistency with user-setup/password-empty (passwd/* really ought to be
renamed to user-setup/* in general; the passwd/* names are historical).
I'll keep compatibility with the old name for one release.
--
Cannot install with
This bug was fixed in the package ubiquity - 1.10.5
---
ubiquity (1.10.5) intrepid; urgency=low
[ Evan Dandrea ]
* Filter out the net subsystem when calling update-dev to prevent the
network connection from resetting (LP: #276383).
* If ubiquity is installing from a disk,
Since Frans hadn't considered the case of embedded devices without
keyboard input, I have no problem with this remaining in place for
Intrepid.
--
Cannot install with a blank password
https://bugs.launchpad.net/bugs/280014
You received this bug notification because you are a member of Ubuntu
** Also affects: installation-guide (Ubuntu)
Importance: Undecided
Status: New
** Changed in: installation-guide (Ubuntu)
Assignee: (unassigned) = Emmet Hikory (persia)
Status: New = In Progress
--
Cannot install with a blank password
https://bugs.launchpad.net/bugs/280014
I've updated the ubiquity branch with a change that preserves the
previous user interaction except in cases where passwd/allow-password-
empty is set to true, in which case the Forward button is enabled while
the password entry is blank. I was unable to expose user-setup
/password-empty in the
** Changed in: ubiquity (Ubuntu)
Status: In Progress = Fix Committed
--
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
** Bug watch added: Debian Bug tracker #501849
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501849
** Also affects: user-setup (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501849
Importance: Unknown
Status: Unknown
--
Cannot install with a blank password
** Bug watch added: Debian Bug tracker #501863
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501863
** Also affects: installation-guide (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501863
Importance: Unknown
Status: Unknown
--
Cannot install with a blank
** Changed in: user-setup (Debian)
Status: Unknown = New
** Changed in: installation-guide (Debian)
Status: Unknown = New
--
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,
The applied fix to user-setup was quite effectively shot down as being
even sensible by Frans Pop in BTS 501849. While I'd personally be happy
not to revert for Intrepid given the timeframe, I'll plan on
unimplementing this and preparing different functionality for Jaunty to
meet the target
Solution proposed in the attached branches is to ass an additional
passwd/allow-password-empty boolean preseed value, and to have user-
setup check this before presenting the user-setup/password-empty error.
The password empty check has been removed from ubiquity. In the event
that a user
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
user-setup change applied, though I merged it too early to include the
bug number. (I've remerged the branch so that it's there for
archaeological purposes.)
user-setup (1.20ubuntu8) intrepid; urgency=low
* Add support and template for passwd/allow-password-empty as a
boolean preseed value
18 matches
Mail list logo
