Comment 64 for bug 66637

fwiw, I disagree with some of the recent marking of duplications of this bug.

As Scott James Remnant states above, this bug is for dapper->edgy upgrades where people have run mkswap by hand. Many of the recent supposed duplications are from people running feisty who've never seen this problem before (such as me).

I think what is happening in fesity is that a hibernate/resume is failing for some reason (or more likely, various reasons), leaving the user with a swap partition that swapon doesn't like (although I can't be sure of that because it seems to have stopped happening to me) and so "correcting" it by resetting their swap, but this of course requires that fstab and /etc/initramfs-tools/conf.d/resume be updated and this (please correct me if I'm wrong) is not documented.

Perhaps mkswap could be patched to warn users that they will need to update these files, or it could be patched to retain the UUID (perhaps with an option to make a new one)