It seems that it's no longer a blocking issue. OEM/ubiquity handles the
error quietly after preseeded installation as shown above (a grep
"encrypt" in /var/log/installer/cdebconf/* gives a few lines about
encrypted home folder errors, but in the end it gets the job done: final
user homedir was crea
I commented the "user-setup/encrypt-home" setting (comment #6) in the preseed
file I used back then, and the user creation step was successful, but I didn't
try to uncomment it again
.
# Set to true if you want to encrypt the first user's home directory.
#d-i user-setup/encrypt-home boolean
This problem does no longer occur after removing the "user-setup/encrypt-home"
option in the tftpboot/pxe config file or in preseed file.
I think it might be trying to encrypt the "oem" user dir which is used at
first start to complete installation but I can't prove it...
--
You received this
** Changed in: ubiquity (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630327
Title:
Ubiquity crashes during final configuration if user requests encrypt
As this bug also affects us here at work, I can reproduce it.
I have found a kind of workaround: at the "end" of the first
ubiquity/oem-config process, when it tries to generate and send a crash report
(which will never end), type Ctl+Alt+F2 to display an active console, then
Ctl+Alt+Suppr to r
Oops, sorry I miss clicked. :-/
** Changed in: indicator-multiload
Status: Invalid => 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/720446
Title:
memory leak in compiz when usin
