and any proposed solution to clear the infamous message 'The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" was useless. But it was not a major problem, at least on my systems, because at the end the swap partition was mounted and was working despite the message. Now, the situation on Trusty is bad, because the cryptswap partition just doesn't work. That's why I don't believe this error should be flagged again as a duplicate of bug #953875.
Well, I've seen a similar bug in Precise for quite a long time:
https:/ /bugs.launchpad .net/ubuntu/ +source/ mountall/ +bug/571682 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/798086 /bugs.launchpad .net/ubuntu/ +source/ ecryptfs- utils/+ bug/953875 /bugs.launchpad .net/ubuntu/ +source/ cryptsetup/ +bug/1061190 /bugs.launchpad .net/ubuntu/ +source/ cryptsetup/ +bug/1153661 /bugs.launchpad .net/ubuntu/ +source/ ubiquity/ +bug/1186811 /bugs.launchpad .net/ubuntu/ +source/ cryptsetup/ +bug/1305961 /bugs.launchpad .net/ubuntu/ +source/ ubiquity/ +bug/1303002
https:/
https:/
https:/
https:/
https:/
https:/
https:/
and any proposed solution to clear the infamous message 'The disk drive for /dev/mapper/ cryptswap1 is not ready yet or not present" was useless. But it was not a major problem, at least on my systems, because at the end the swap partition was mounted and was working despite the message. Now, the situation on Trusty is bad, because the cryptswap partition just doesn't work. That's why I don't believe this error should be flagged again as a duplicate of bug #953875.