Comment 23 for bug 1447282
Revision history for this message
| Jason Gerard DeRose (jderose) wrote | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Some more details: I tested 3 scenarios, all starting with an OEM mode install. The first 2 worked fine, the 3rd seems to have some issues:
1) Install all current updates in proposed from the OEM account, then prepare for shipping to user, then create a user account with an encrypted home directory. No issues.
2) Prepare for shipping to user, then create a user account with an encrypted home directory, then install *only* ecryptfs-utils, libecryptfs0 from proposed. No issues.
3) Prepare for shipping to user, then create a user account with an encrypted home directory, then install *all* updates from proposed. The systemd update is prompts for the encrypted swap passphrase twice and results in a package error (an indicator pops up with the error), although after a reboot things seem to probably be fine.
I ran scenario (3) from a terminal, still need to see what happens when I run it from the update-manager. Also, if you don't enter your passphrase (or at least press enter, the passphrase seems to be ignored anyway), the prompt will hit a timeout and the update will fail. So my biggest concern in running this from the update manager, will try that now...