Resume from encrypted swap fails

[Psychotron]

I'm using (K)ubuntu 8.04.1 Hardy, freshly installed from the alternate iso.
lsb_release -rd:
Description: Ubuntu 8.04.1
Release: 8.04

I can't resume after hibernation. Hibernate itself seems to work fine (at least mounting the encrypted swap complains about a suspend signature on the device, see below). However on restart it doesn't seem to actually do a resume, but a normal startup.

I created two encrypted partitions with the alternate installer:

/dev/mapper/sda2_crypt as root and
/dev/mapper/sda9_crypt as swap

I don't use LVM. Booting and mounting both partitions works fine as long as I don't hibernate. However if I do, on startup I get:

[...]
[successfully unlocking root]
Done.
Begin: Running /scripts/local-premount ...
Begin: Waiting for resume device... ...
Done.
Done.
[successfully mounting root]
[...]
 * Starting early crypto disks...
Enter LUKS passphrase:
key slot 0 unlocked.
Command successful.
 * sda9_crypt: the check for '/dev/mapper/sda9_crypt' failed. /dev/mapper/sda9_crypt contains data: - The device /dev/mapper/sda9_crypt contains a valid file system type suspend
 * Starting remaining crypto disks...
[another try for sda9_crypt, fails same as above]

I don't know how the boot process for resume should look like, but to me it seems as if it's just the normal boot procedure, and that unsuprisingly fails i.e. as if it's not performing a resume at all! The resume device seems to be ignored. I tried specifying different resume parameters in grub, but couldn't find one that worked. (I couldn't find out what exactly it should look like for encrypted swap partitions, though.)

[papukaija (papukaija)]

Coonfirming with a fresh Ubuntu Karmic install (using the encrypted home directory option in the installer).

[papukaija (papukaija)]

This bug might be caused by bug 461442.

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It is currently a known issue that Hibernation will fail to resume due to an encrypted swap. Developers are hoping to resolve this issue for the Lucid Lynx 10.04 release. Please refer to https://help.ubuntu.com/community/EncryptedHome for more information. Thanks in advance for your patience and cooperation.

[Psychotron (redm)]

I'm not sure this is same problem as bug 432785. AFAICS the Hard alternate installer created a static encryption password for swap, which I had to enter all the time (not that convenient, but that's a different topic). On resume the swap disc is successfully unlocked. However, no resume takes place.

I can't quite check anymore what exactly was going on. I went for a working solution in the meantime, as I didn't have the patience to wait 2 years for the problem eventually being fixed..