Problem restoring laptop state after lid re-opened

[g40]

The desktop appears to freeze once the lid is re-opened. The mouse still works but keyboard appears disabled. The only solution so far is power-cycle.

Using power manager I have tried each option, all end up with the same result. Screen locking is off.

[edit] The 'switch off display' option *does* work, but suspend/hibernate/lock all seem to skewer the desktop.

Any thoughts? Machine in question is an Intel i5 Dell Vostro w/ 16GB RAM, Samsung 512GB SSD. Please let me know if more info required.

[Şerban S.]

[...] Machine in question is an Intel i5 Dell Vostro w/ 16GB RAM, Samsung 512GB SSD. Please let me know if more info required.

Is it possible to use the Terminal?
If YES, than type:

Code:

df -h

Then copy and paste the result in a new post here.
From the info provided, it is likely that the space available to perform this kind of task, is too low.
Read the manual and see what means "Sleep".  The system state is copied and this takes a lot of space. Usually, it takes at least 10 GB of space, maybe more, depending on what is installed.

Briefly:

"systemctl hybrid-sleep suspends the system both to RAM and disk, so a complete power loss does not result in lost data. This mode is also called suspend to both. systemctl suspend-then-hibernate initially suspends the system to RAM as long as possible, then wakes it with an RTC alarm and hibernates."
That means that you need plenty of RAM, too.
Is 16 GB enough to store all data? As i said before, depends on the amount of the installed applications and the number of the running ones, the number of opened documents.
The most space consuming is the browser. So, if you put the computer to sleep with lots of documents opened in your browser, this is the result you get.
Another possible reason, is the state of the drive. If the drive is old, this meaning it has over 15,000 hours of service, the reliability is low and many errors can occur when performing the Sleep task due to read/write errors.
Unfortunately, the diagnostic tools will warn you only if there are bad sectors. Otherwise, the report will say "The drive state is perfect".

Best regards, Șerban.

[g40]

Hello Serban and thanks for the help. There is plenty of space

Code:

df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1.6G  4.7M  1.6G   1% /run
/dev/sda2        89G   27G   58G  32% /
tmpfs           7.8G   29M  7.8G   1% /dev/shm
tmpfs           5.0M  8.0K  5.0M   1% /run/lock
/dev/sda1       511M  6.2M  505M   2% /boot/efi
tmpfs           1.6G  112K  1.6G   1% /run/user/1000

```

[stevef]

To narrow the problem down, have you tried testing suspend and hibernate operation without using Power Manager and opening and closing the lid.
Using the terminal to initate the operations allows you to see any error messages.

To test Suspend operation, open a terminal and try the command

Code:

systemctl suspend

This should save the system state to RAM and go low power mode within a few seconds.
The RAM must remain powered up.  Pressing any key should restore the desktop and allow operation.
Exit from suspend should happen in a few seconds.

To test Hibernate operation the command is

Code:

systemctl hibernate

This should save the system state to disk and power down.  This will take a little longer.

If these work correctly, it suggests the Power Manager and Lid complications needing testing.
If they don't work properly, then the problem needs to be diagnosed before moving on to Power Manager.