When my battery is critically low, Solus hibernates, but after I plug in my laptop, everything seems frozen and slow/laggy. I have to force my laptop off by holding the power button and restarting and fortunately none of my Firefox tabs get lost. When I was on Linux Mint, it restored from Hibernation much better. Maybe this is happening because I installed Solus 2017.01.01.0 originally ? Can this be fixed by applying updates or would I have to reinstall Solus ?
Description
Description
Related Objects
Related Objects
- Mentioned In
- T5010: Meta: Solus 4 Tasklist
Event Timeline
Comment Actions
I manually pressed Hibernate now and after my laptop turned off and I pressed the power button, it started again normally as though I had shut down. It should have shown a message saying "resuming from hibernate" or similar and shown System Monitor and Firefox open after I entered my password.
Comment Actions
We've sinec then had several and also a major update to mate, is this still largely an issue or is it resolved?
Comment Actions
Yes it's still broken with Mate 1.20 and all updates installed. In power management settings I changed it to suspend when critically low on battery so that my session is saved until I plug into a power source.
Comment Actions
I see this when it's about to suspend:
And when I woke from suspend, everything was slow and I had to force shut down my laptop.
And I think the " <br><b>NOTE:</b> " is meant to make part of that notification text bold ? I guess that's a Mate bug.
Also when I set "When battery power is critically low" to Suspend like this:
I see this when it's about to suspend:
And when I woke from suspend, everything was slow and I had to force shut down my laptop.
And I think the " <br><b>NOTE:</b> " is meant to make part of that notification text bold ? I guess that's a Mate bug.
Comment Actions
I installed Solus 3 Mate on my new ThinkPad E480 and hibernate doesn't work when I click it manually.
It just looks like the screen gets locked.
Comment Actions
In Solus3 era I experienced a bug with Live USB install where setup program would fail to initialize swap partition, and this partition is where memory content is "hibernated". To make hibernate work I had to do one time fix: swapon and add kernel parameter resume=UUID=swap-parttion-uuid. @mate-user, If your install is that old root cause of your problem may well be missing/unused swap partition, like I used to have. If you never fixed swap partition manually, fresh install of Solus4 will definitely help.
Comment Actions
This is a very long thread, and I haven't read every message, but is it possible your swap is using a file instead of a partition? I'm pretty sure I've inadvertently told a machine to hibernate that did not have a swap partition defined, and it did, but it was very slow.