Seeing "swap: waiting for /dev/mapper/cryptswap1" for several seconds while booting

I'm having the exact same issue.

Same message but after a fresh install of Ubuntu Karmic RC.
I checked the encrypted option for my home folder during the installation.

I have the same error under the same conditions. Additionally, while setting up a swap partition to try allowing for hibernation, I received this error when executing "swapon -a":
# swapon -a
swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

This bug seems to cause mounting the swap partiton to fail (since recent updates). See bug 460745 for more information.

I have a grub multiboot system and share a single 2GB swap partition between hardy, jaunty and karmic. The cryptswap wait is much more likely to hang forever when booting karmic after karmic. If the swap partition has been previously formatted by one of the older, non-crypt systems, it seems to me that the cryptswap wait will eventually end normally and the boot process will complete successfully. (I will observe more carefully from now on and let you know).

Still not clear what the pattern is... howver, whenever I've had a system that hung in boot because swap was "wrong", I've got out of it by doing a boot in recovery mode. It appears that a recovery boot serialises well enough that the system waits until swap/cryptswap is formatted properly.

Workaround (if your swap wasn't mounted): "sudo swapon -a" after that your swap will be shown by "sudo swapon -s".

Workaround (tongue in cheek): if your system hangs and the disk activity light stays on for 10 minutes or more - press the power button and hold it down for 5 seconds!!!

My symptoms look more like a race condition caused by an implicit assumption about how long it takes to format the swap partition, rather than waiting for the task to complete... Should I open a new bug?

I'm with the same bug here. This errors began with the more recent updates.

The lastest update solved this problem for me.

The new kernel 2.6.31-16-generic is working perfectly.

sorry, but in the second boot the trouble is back. My solution is using the "noauto" option in fstab.

I have the same exact message. I used home encryption and the next shutdown I did after first starting gave me this problem. I am stuck in an infinite loop of reentering my password. It will not login! The only thing that happens is that the screen turns black and something flickers. It resembles a tab you would see on Firefox. Then more blackness and my login screen. I can't get access. This problem isn't solved.

Note: maybe when ubuntu checks the disc, it causes this problem.