mate-desktop / mate-power-manager

Power management tool for the MATE desktop
https://mate-desktop.org
GNU General Public License v2.0
59 stars 52 forks source link

Hibernate instead of suspend #183

Open shayanh opened 8 years ago

shayanh commented 8 years ago

I have Manjaro 15.12 with Mate 1.12.1 on Thinkpad X250

In Mate Power Manager I have set to put computer to sleep when it is inactive for 30 minutes. But instead of sleep, my computer goes to hibernate mode and I have problem with hibernation and my computer doesn't wake up correctly from hibernate.

I want my computer goes to sleep as I configured in Mate Power Manager, not going to hibernation.

How I can fix this problem?

Thanks in advance

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

monsta commented 8 years ago

Interesting - I saw that on one of my machines and thought it's some local hardware issue on my side. The distro is different (LMDE 2, based on Debian Stable). I'll check it once more...

shayanh commented 8 years ago

Before Mate, I had XFCE on my machine and mentioned feature works correctly.

monsta commented 8 years ago

Indeed, it still happens on that machine... not sure why, but Hibernate and Suspend buttons in shutdown dialog seem to be switched. :confused:

monsta commented 7 years ago

Ok, now I don't see it anymore. Can you still reproduce it? Since you have Arch-based distro, you should have the latest MATE now.

joancf commented 7 years ago

I have a linux Mint 18 and on battery power it hibernates instead of suspend. Does not do so in AC mode, or running ubuntu or cinnamon I have an SDD and 16G of Ram so I'm not very happy of writing such a quantity of data? I use MATE Desktop Environment 1.14.1

monsta commented 7 years ago

Maybe try Mint 18.1 with MATE 1.16?

joancf commented 7 years ago

yes I tried, but the same problem persists :-(

Joan

flexiondotorg commented 7 years ago

@monsta Ubuntu deliberately disables Hibernate because it is known to not work reliably. Does Mint override this?

monsta commented 7 years ago

I'm not aware of such override, but I can see hibernate as an option in mate-power-preferences. Though Mint 18.x releases are based on Ubuntu 16.04. Maybe there was no override in that Ubuntu release?

monsta commented 7 years ago

At least setting it to suspend on pressing Power button seems to work here. Hibernate option works as well.

monsta commented 7 years ago

Suspend on idle option works in my Mint as well, so the original issue seems to be fixed. It's a desktop machine, so I can't test the behavior on battery power.

ghost commented 6 years ago

From a terminal, execute gsettings set org.mate.power-manager action-sleep-type-battery 'suspend' which should tell the Mate Power Manager to suspend-to-RAM instead of hibernating to disk.

monsta commented 6 years ago

@joancf @shayanh @flexiondotorg Can you test what's suggested above?

bwat47 commented 6 years ago

I had the same problem (Mate 1.20, Solus Linux). I can confirm that the gsettings change ghost mentioned fixed it for me.

It seems like there is a bug if that gsettings key is set to hibernate even though the dropdown in the mate power settings for what to do on idle on battery is clearly set to suspend?? Shouldn't adjusting that setting set that key to suspend?

lukefromdc commented 6 years ago

Keep in mind, hibernation is only possible with a swap partition at least as large as installed RAM. On machines today with very large amounts of RAM this can be an issue. Also lots of installs today are set up with no swap at all.

cantalupo555 commented 6 years ago

systemctl suspend As our friend said, you need SWAP free.

Currently I follow a default: 2GB RAM = 2GB Swap 4GB RAM = 6GB Swap (Above 2 GB, I add twice as much memory + 2GB Swap) (4+2) 8GB RAM = 10GB Swap (8+2) 16GB RAM = 18GB Swap (16+2)

coozoo commented 6 days ago

From a terminal, execute gsettings set org.mate.power-manager action-sleep-type-battery 'suspend' which should tell the Mate Power Manager to suspend-to-RAM instead of hibernating to disk.

Damn this old bug I'm still using this settings and it is almost 8 years since initial report