Installing over ecryptfs-enabled system causes remove_extras to fail.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ecryptfs-utils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| partman-target (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| ubiquity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| user-setup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Please accept a freeze exception for the following changes:
http://
http://
http://
There exists a bug wherein if you install with an encrypted home directory, then install again without formatting / or /home, but do not elect to use an encrypted home directory, the installer will crash. This is because we do not clear files from the home directories in this partitioning method, and the ecryptfs-utils prerm fails when it sees ~/.ecryptfs. The solution is to force the user to use encrypted home if they used it in the previous system and are not removing their encrypted home directories.
This does not affect the alternate CDs as it requires ecryptfs-utils to be copied to the target system and removed, which ubiquity does as a result of the nature of its design.
I've tested this in a virtual machine with both the desktop CDs to make sure that it forces the selection to the encrypted home option, and to make sure that the install is able to complete successfully. I've also tested the changes with an alternate CD to make sure that it's unaffected.
The original report follows:
Binary package hint: ubiquity
I installed with the "encrypt my home directory" option enabled, then installed over top of that with automatic login enabled and the root partition marked as "do not format". This causes the ecryptfs-utils prerm to fail inside ubiquity, as ~/.ecryptfs exists (we don't delete it in clear_partitions).
This results in an error message (http://
| description: | updated |
| Changed in ubiquity (Ubuntu): | |
| milestone: | none → ubuntu-10.04 |
| Changed in ecryptfs-utils (Ubuntu): | |
| status: | New → Invalid |
| Changed in partman-target (Ubuntu): | |
| status: | New → Fix Committed |
| Changed in ubiquity (Ubuntu): | |
| status: | New → Fix Committed |
| Changed in user-setup (Ubuntu): | |
| status: | New → Fix Committed |
| Steve Langasek (vorlon) wrote | #13 |
| Steve Langasek (vorlon) wrote | #15 |
| Launchpad Janitor (janitor) wrote | #16 |
| Changed in user-setup (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #17 |
| Changed in partman-target (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #18 |
| Changed in ubiquity (Ubuntu): | |
| status: | Fix Committed → Fix Released |
Is the freeze exception for the fact that we're in final freeze, or are there changes here that you wouldn't consider straightforward bugfixes?