Trust me, I have identified the whole of the problem after enabling full trace of the relevant scripts and going through the logs with a fine tooth comb. The bug is not *in* Ubiquity therefore it is incorrect to leave it tasked there. The Ubiquity developers do not need to know about it as they can not fix it. It also would still say there is a problem in ubiquity after it is fixed in partman-crypto. Unfortunately launchpad does not have the capability to record that a bug affects another package without actually being in that package and needing to be fixed in that package.
** No longer affects: ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523194 Title: Can't install /home into separate LUKS encrypted volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/1523194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
