I had a problem with hibernate myself on an upgrade from dapper to edgy whereby a) hibernate wouldn't happen just as you describe, and b) when I fixed that, the machine would screw up on resume and just reboot normally without restoring my hibernated session.
I think it can get into state a) when there is a hibernated image on your swap partition, but the kernel hasn't been told to use it on reboot. This causes the *now normal* reboot to disregard the swap partition, and this causes future hibernate attempts to fail. *** Could you open a terminal and do a: $ cat /proc/swaps $ sudo swapoff -v -a $ cat /proc/swaps $ sudo swapon -v -a $ cat /etc/fstab and then attach the results here as a .txt file? BTW, "$" is your terminal prompt; don't type that! IIRC, I fixed a) by making really sure that I had swap space available, and that it was actual swap space. IIRC, I fixed b) by making sure I had the right "kopt" parameters for enabling resume on boot from the right partition. *** Could you also make a copy of your "/boot/grub/menu.lst file", "XXX"-out any sensitive information like passwords, and attach it to this ticket? Thanks. -- Wont suspend (or hibernate), won't say why, and is annoying. https://launchpad.net/bugs/50785 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
