I have a new HP ProBook 450 G3 15.6″ Laptop.

I installed Ubuntu 16.10 Gnome on it. I'm using a SSD (no spinning disk). The laptop doesn't Suspend (i.e. Suspend-to-RAM) when I shut the lid and carry it elsewhere. When I get to my destination either the laptop is hot or the battery is dead.

I know that shutting the lid can cause a number of different states (sleep, suspend, hibernate). I believe that what I want is correctly called Suspend-to-RAM (monitor off, and details saved to RAM for a speedy return to work). This laptop, on lid-close, shuts off the monitor but all else continues working.

When I call up "gnome-tweak-tool" the setttings appear to be correct (i.e. they tell the laptop to suspend-to-RAM when I close the lid)
"When laptop lid is closed
- On Battery Power - Suspend
- When Plugged In - Suspend
Don't Suspend on Lid Cose - Off"
When I changed "Suspend" to "Hibernate" the laptop continued to do nothing except shut off the monitor when I close the lid.

How can I do that? I found some out of date posts on this but no solution yet.
In Settings / Power I see "Power" and "Suspend and Power Button" but no place to specify action to occur on lid-close. I tried Gconf-Editor but I wasn't able to find the correct settings.


Based on www DOT linux DOT com/news/how-suspe...op-under-linux
I think this is relevant
Code:
$ cat /sys/power/state
freeze mem disk

Seems relevant too:
wwwDOTkernelDOTorg/doc/Documenta.../interfaceDOTtxt I read that
/sys/power/state is the system sleep state control file. it returns a list of supported sleep states, encoded as:
'freeze' (Suspend-to-Idle)
'standby' (Power-On Suspend)
'mem' (Suspend-to-RAM)
'disk' (Suspend-to-Disk)

Depending on how you did your install, the tools needed to do that may not have been installed (most desktop users don't need it). The acpi side of things handles events AFAIK, like issuing shutdown when the power button is touched. And suspend when the lid is closed. I actually like my laptop to NOT suspend when I close the lid. But most of my laptops have 6+ hours of battery life and are the fanless silent types.

$ sudo apt-get install acpi-support

$ acpi-support is already the newest version (0.142)

I always get them backwards, but suspend and hibernate are two different things. One saves RAM to disk (swap). The other wakes up and keeps RAM alive every minute plus which continues to burn battery life, just a lot slower. It sounds like you want the one that writes ram to disk, which likely requires swap space at least as big as your RAM. Otherwise it probably wont do that option.

My better half has a HP something-or-other (touch screen, folds right over so as to be a tablet) - similar symptoms running Mint Mate. I eventually deduced that the lid-close wasn't being detected. But lid-open is.
I set the power button to suspend and she eventually got used to using it. Does the job, and it fires back up when the lid is opened.

I gave up chasing a reason.

I'm not an Ubuntu user, but AFAIU systemd is in use so the lid-close behaviour can be controlled via /etc/systemd/logind.conf configuration. Look for the entry '#HandleLidSwitch=' and uncomment it. Valid options are

For more info refer to

I went to "uncomment" it, but they seem to be ALL "commented".
Anyway, I used "sudo nano /etc/systemd/logind.conf" to uncomment "HandleLidSwitch=suspend" and save the revised file. I closed the lid, waited a few seconds and opened it. It had not "suspended".

To complicate the situation, when I left the lid closed for a long time, like a couple of hours, when I came back it seems to me that the laptop had suspended (a brief press on the power button woke it up) but then the computer froze and I had to do a "hard restart" anyway.

Do you have swap space? Is it at least as big as your RAM capacity? One reason that it might fail.

Normally commented out "options" are set to the default option. So commenting them out does basically nothing unless you change the other side of the option. When making edits to those I duplicate the commented line and change the duplicate, that way I always know what the default was and that it was customized. But I also tend to add a comment with my initials and a date/time stamp. For things that I might want to do again someday. But mostly I avoid magic configs. If a distros defaults doesn't work for me, I find another distro.

when you edit config files, it is quite common that the daemon reading them needs to be reloaded manually.
not sure what it would be in this case; maybe 'systemctl restart logind', maybe sth else.

Well yes, that's just the default configuration The administrator can configure as they like.

A reboot (or restarting logind) would have been needed for this to take effect.

This suspend event was probably desktop-related configuration (eg my laptop is configured to suspend after X minutes when on battery), but in any case you may have additional suspend/resume issues to sort out from here.

Thanks for the response.

By now I've rebooted a few times and the suspend/resume problems continue.

My present situation
1. My laptop does not automatically suspend-to-RAM when I close the lid.
2. It does suspend sometimes, apparently after some specified time period, I don't know what
3. It does not resume from the suspend, I'm usually faced with either a properly displayed monitor image (which is frozen) or a dark monitor (but some of the laptop lights are lit suggesting that it is "awake")

Where do I go from here?

This I do find surprising. However, there have been some regressions reported like this one. Perhaps you're similarly impacted. A bug report may be necessary to help resolve.

That is likely to be a desktop related setting. Which DE are you using?

Suspend/resume issues like this are often caused by a graphics-related issues. A separate thread ideally. You should start by sharing your graphics hardware details (chipset/driver)

One way to get that info...

I'm using Gnome

$lshw gave me
*-display
description: VGA compatible controller
product: HD Graphics 520
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:127 memory:e1000000-e1ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff

Further details here:
https://hastebin.com/conuvubone.http

When I create the new thread I'll put a link here.

Ok, so Intel Skylake graphics hardware. A quick search turned up this bug report which may be relevant to you...
https://bugs.launchpad.net/ubuntu/+s...x/+bug/1589379

Another long-running bug report concerning broken laptop suspension...
https://bugs.launchpad.net/ubuntu/+s...d/+bug/1574120
Comment #79 onwards mentions the problem still existing in 16.10 for various laptop models.