Questions[resume](ubuntu)

Why don't I have a resume file in the path: /etc/initramfs-tools/conf.d? Shouldn't there be in this path?

I'm using Ubuntu 20.04 and while installation I created a swap partition (instead of swapfile) that is regularly in use, in fact the output of swapon -s is:

Filename                Type        Size    Used    Priority
/dev/sdb5                               partition   9765884 0   -2

N.B.: Actually I'm looking for this file because I want to migrate from swap partition to a swapfile, and for this purpose I found some simple instructions which, at the end, also suggest to edit this "resume" file (that I don't have)!

How to get date/time of these events:

• last system hibernate / suspend
• last system resume

Running Ubuntu 18.04, I changed from a swap partition to a swap file.

swapon -s (summary) and free show the swapfile with the new size. /etc/fstab was changed, permission on the swapfile changed and the swap partition was deleted. When there are updates (apt-get update and upgrade), I get this error:

Setting up amd64-microcode (3.20180524.1~ubuntu0.18.04.2) ...
update-initramfs: deferring update (trigger activated)
amd64-microcode: microcode will be updated at next boot
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-29-generic
W: initramfs-tools configuration sets RESUME=UUID=c5a2c6f4-b67c-4d95-bc23-8333ed6c0f11
W: but no matching swap device is available.

The UUID listed there is for the old swap partition. I didn't think a swap file has a UUID, but I am not sure about that. Everything else seems to work fine. How should I proceed to troubleshoot and fix this?

After completing a fresh install of Ubuntu 18.04 LTS and rebooting, I closed the Acer Aspire ES1-511 laptop lid and took a little break. When I came back to continue exploring the new features of 18.04, the Laptop would not turn on. One of the internal fans was running quite loudly, but nothing more. I had to reboot once again.

This seems to be a recurring problem through the years of Ubuntu. I've looked into the issue since, first trying to change power settings in gnome-control-center and gnome-tweak-tool, then installing pm-utils, editing system files supposedly responsible for suspension, and plenty more attempts, all to no avail. I even tried running Ubuntu 18.04 Live from a USB drive, and the same problem still occurs.

I suspect it's an issue with the kernel, as I've seen this problem in the past with the kernel 4.15. Would an upgrade to the latest Linux kernel or a downgrade to a more stable version solve the problem? Has the problem been patched? Maybe I can just edit some file and this whole thing would be solved...

Some specifications: The Kernel currently running is 4.15. The computer, as mentioned above, is an Acer Aspire ES1-511. Desktop environment is Gnome 3.28.1. Ubuntu version is 64-bit 18.04.1 LTS.

Any help is appreciated. The computer is losing a lot of sleep over this.

I have a Dell Inspiron 2650 (with NVidia graphics, using nouveau drivers) that I'm using to try out Ubuntu. It's all great, except that Hibernate and Suspend aren't usable.

Yes, I know that questions about power-save issues are rampant in the Linux support universe, but it seems that every time I find a solution it's for a very specific hardware combination and doesn't apply to me. So anyway, here goes.

When I resume from either power-saving mode, I'll get graphics problems anywhere on the range from a few scattered random-colored pixels that won't change; all the way to full-screen patterns that don't change as I move the mouse, hit keys on the keyboard, or even bring up the shutdown dialog using the power button.

Those full-screen issues (which may involve stripes with random pixels, partial black screen, or both) always end in me forcing the machine to shut down by holding the power button.

I haven't done much testing yet to determine what severity level is most commonly associated with each mode, but I do avoid using either power-save option because of these issues.

I'll add info on my hardware as I can gather it (no home internet connection, and this laptop is tethered to my desk by a dead battery and casing degradation). Please feel free to request something specific in the question comments.

Hardware Info

See this hardinfo report for my system's hardware configuration. (No, my username is not "myuser"; I sanitized hardinfo's output before publishing it.)

Screenshots

These screenshots are from a relatively mild occurrence, which happened after the second hibernation I took that session. The first one worked great, though I used the wireless card and Firefox heavily between the two hibernation attempts.

Take a look at what happened when I opened my home directory in Nautilus and scrolled it:

See below for the situations I've tested so far. The real trouble comes when the machine resumes to an unusable state; in such cases I can't even unlock the screen or properly reboot, much less take a screenshot. I have a hunch that putting a CD in the drive will cause such major failures, and I will try that at some point; see related question.

Situations Tested

Maverick (10.10)

• Seems to suspend nicely with nothing running
• Seems to suspend nicely with flash drive plugged in
• On resume from suspend with no flash drive, Terminal and gedit running: Funky graphics on top of log output, then blank screen with pixelated cursor; no response to power button (normally will shutdown 60 seconds later)

• Seems to hibernate nicely with nothing running
• Seems to hibernate nicely with a few apps (Terminal, Mouse preferences) running
• Seems to not hibernate when flash drive plugged in
• Seems to not hibernate when System Monitor is running
• Have encountered failed hibernation (after several hours and one successful hibernate/thaw cycle) with no external media connected and no programs running except normal background stuff

Natty LiveCD (11.04_2010-12-22)

When I tested it, Natty wouldn't stay logged in. It played part of the login sound and then [ OK ] appeared in the top right corner (white-on-black terminal text) for a few seconds. Then it kicked me back to the Unlock screen. It did that four times before I gave up and just tested suspend from the Unlock screen.

• Resumed to vertical gray and black lines 2px (?) wide, then shifted to vertical "jail bars" of black over a black screen with above-described random pixels and mouse pointer. No apparent response to input from mouse (clicking randomly). Keyboard and touchpad unrecognized.