This seems to be reported rather consistently, and is not a case of a
misconfigured crypttab: all users reporting this issue show a crypttab
that correctly sets up their crypted swap, *and* swapon -s shows that
the swap is enabled successfully after boot. But for some reason
mountall thinks it hasn't been activated, which means the boot stalls.
We should definitely get this fixed.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Triaged
** Also affects: cryptsetup (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: cryptsetup (Ubuntu Precise)
Importance: Medium
Status: Triaged
** Tags added: rls-mgr-p-tracking
** Changed in: cryptsetup (Ubuntu Oneiric)
Assignee: (unassigned) => Ubuntu Foundations Team (ubuntu-foundations-team)
** Changed in: cryptsetup (Ubuntu Oneiric)
Status: New => Triaged
** Changed in: cryptsetup (Ubuntu Oneiric)
Importance: Undecided => High
** Changed in: cryptsetup (Ubuntu Precise)
Importance: Medium => High
** Changed in: cryptsetup (Ubuntu Precise)
Assignee: (unassigned) => Ubuntu Foundations Team (ubuntu-foundations-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874774
Title:
could not mount /dev/mapper/cryptswap1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
