https://www.linuxquestions.org/quest...nd-4175642245/

After solving this problem,there arises another problem.When waking after hibernation,all my applications are closed like being shutdown.I found a similar problem on another forum and tried the method mentioned in the post for hibernation instead of suspend.
https://askubuntu.com/questions/7200...upon-awakening
There is no problem for suspend but it doesn't work for hibernation.

How do I solve this problem? Any new ideas are welcomed.

My initial guess would be that it is not actually going into hibernation. Other idea may be that some distro or user setting is telling it to close on hibernate and that would be odd.

Usually the problem is some deal between bios/motherboard and the OS acpi.

Might have to test a clean install and be sure to see what S states your system has and if your boot to linux has correctly selected acpi and the availability to select swap partition.

I'll ask this too. You aren't using some live cd or usb pendrive deal?

Try debugging or set hibernation to never:-

https://01.org/blogs/rzhang/2015/bes...bernate-issues

1 members found this post helpful.

I just installed windows too and rebuild ubuntu GRUB. So now as I try to hibernate, I see that it restarts and go to the page where it asks to select which OS I want to use. I have tried a lot trying to install ubuntu. If I can figure some ways without having to install again,that's great else,I will try suspend instead of hibernate.

Hibernation makes an image of your current situation, saves this to an image file which then starts again.

It is perfectly normal that you have to choose your startup in grub, even when using hibernation. When you select whatever same boot that you hibernated with, it will open the hibernation file and start you up where you were.

I don't use hibernation because I like suspend, and I am no expert on hibernation, but as far as I understand your boot settings have to be correct for it to work. On the entry you use hibernation and then restart you must have the correct "resume=/dev/xxx" boot prompt for it to work. I think.

Correct. The partition that is used for the dump is your swap partition, so that is what you have to give as the "resume" device. Also it must be big enough to hold a complete memory image. Your machine seems to be rebooting rather than resuming so maybe you have specified the wrong device. dmesg should say what partition the kernel was trying to resume from.

I suspect that you are in the same boat as me. I used to be able to suspend to disk and resume on an old netbook that I use. Somewhere between kernel 4.14.56 and 4.14.62, a regression occurred in the kernel, so that the resume proceeds until the image is restored, but then the screen goes blank and the system reboots.
The problem is likely to be a hardware quirk, but I have not felt motivated to do the kernel git bisect to isolate the problem.
My advice, try kernel 4.14.56 to see if the the problem is resolved.

I also guess it cannot be encrypted.. As there is no way for GRUB to decrypt a partition..

And yes, if the "resume=dev/xxx" is not correct, the system will just restart your distribution, right.. Is it always the swap partition?

I think it has to be either a swap partition or a swap file.

I think we gave OP a few things to think about here.. Maybe enough to get this situation resolved. Let's hope so!