OK, so I have a fix for the ubiquity side of things, but the swap setup post-reboot still doesn't work. However, I think that's something that needs to be fixed elsewhere. I started a conversation with Dustin about it on IRC and we'll see where that goes:
14:53 <cjwatson> kirkland: so, bug 1172014 14:54 <cjwatson> kirkland: this change caused a regression in ubiquity; not really your fault, ubiquity needed to resolve the UUID= in crypttab because it explicitly zeroes the device 14:54 <cjwatson> kirkland: but more importantly, I can't actually make the swap setup work properly even after fixing that ubiquity bug 14:56 <cjwatson> kirkland: I think https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1172014/comments/9 has the right of it; the swap space is set up with a random key, there's no container, so how can it have a stable UUID? 14:58 <cjwatson> kirkland: indeed when I reboot after installation, re-point crypttab to /dev/sda5 so that I can cryptdisks_start, copy the new UUID into /etc/crypttab, and reboot, it still doesn't work ** Changed in: ubiquity (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296697 Title: Trusty Desktop installer crashed with "Encrypted Home" set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1296697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
