Ubiquity fails to create encrypted home directory when no swap if configured

Thanks for your report. I can reproduce with your steps. Setting to 'medium' because there is a big warning in the manual partitioner when the user continues without swap.

The big warning says nothing about ecryptfs problems, so your reasoning is false. Anyway, this warning has been there like forever and the described problem appeared in this very version. It also affects current users (like me) with plenty of RAM, who know very well that upgrading Ubuntu is asking for problems and want to clean install a new version, while keeping their encrypted home intact. It's the first time since I can remember that it doesn't work.

Really, ubiquity shouldn't even try to set up encrypted swap if there is no swap.

This bug was fixed in the package ubiquity - 2.11.15

---------------
ubiquity (2.11.15) quantal; urgency=low

  * Drop hw-detect debugging attempts.
  * Terminate status-to-debconf subprocess in DebconfInstallProgress more
    gracefully to avoid desynchronising the debconf protocol if the
    subprocess is killed between sending a command and receiving the
    response (LP: #1023036).
  * Make user-setup-encrypted-swap wait until partitioning has finished
    before attempting to adjust /target/etc/fstab (LP: #1024343).
  * Don't try and fail to set up encrypted swap if no swap partitions are
    configured (LP: #989279).
 -- Colin Watson <email address hidden> Sat, 14 Jul 2012 00:17:31 +0100

Hello amay82, or anyone else affected,

Accepted ubiquity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubiquity/2.10.18 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

SRU verification for Precise:
I have reproduced the problem with ubiquity 2.10.17 in precise-updates and have verified that the version of ubiquity 2.10.18 in -proposed fixes the issue.

I verified that the crash is fixed, after installation there is no swap and home directory is encrypted.

Marking as verification-done

This bug was fixed in the package ubiquity - 2.10.19

---------------
ubiquity (2.10.19) precise-proposed; urgency=low

  * Automatic update of included source packages: base-installer
    1.122ubuntu7.1, debian-installer-utils 1.88ubuntu2.1, flash-kernel
    2.28ubuntu42.2. (one-time update from precise-proposed) (LP: #1021293)
 -- Stephane Graber <email address hidden> Mon, 30 Jul 2012 10:36:51 -0400

the situation is similar to new lubuntu 13.10 x86

this is my /var/log/syslog:

Oct 26 08:47:41 lubuntu ubiquity: 2463
Oct 26 08:47:42 lubuntu ubiquity: WARNING: [/dev/zram0] is a RAM device, skipping.
Oct 26 08:47:42 lubuntu ubiquity: WARNING: There were no usable swap devices to be encrypted. Exiting.
Oct 26 08:47:42 lubuntu ubiquity: /usr/share/ubiquity/user-setup-encrypted-swap: 79: /usr/share/ubiquity/user-setup-encrypted-swap:
Oct 26 08:47:42 lubuntu ubiquity: cannot open /etc/crypttab: No such file
Oct 26 08:47:42 lubuntu ubiquity: cp:
Oct 26 08:47:42 lubuntu ubiquity: impossibile eseguire stat di "/etc/crypttab"
Oct 26 08:47:42 lubuntu ubiquity: : File o directory non esistente
Oct 26 08:47:43 lubuntu ubiquity[2463]: debconffilter_done: ubi-usersetup (current: ubi-usersetup)
Oct 26 08:47:43 lubuntu ubiquity[2463]: dbfilter_handle_status: ('ubi-usersetup', 1)