New answers tagged hibernate
You can clear the hibernated session by cleaning the swap partition (if isn't cleaned) you can know what is your swap partition by running: lsblk -f | grep swap ├─sda5 swap 81ede0e2-2b07-4986-9a98-cea7a5b22556 [SWAP] Then, you can clear it: mkswap /dev/YOUR-SWAP-PARTITION
May be your grub installation is corrupted. I would try to reinstall grub2: apt-get --reinstall install grub2 If I can add, would not rule it took to check the integrity of fs in the partition in question. fsck /dev/sdaX
Albert, Suspend is a "warm resume" meaning the system is still "active" merely cat nappign "with one eye open " to use the common phrase" whereas, with hibernate the system is totally shut off adn has the " Don not distrub me room service people " mentality
I found a solution to my question on my own. SOLUTION Wrote in terminal: sudo ntfsfix /dev/sdXY where sdXY is the partition I needed to mount, in my case - DATA partition. With this I can hibernate windows and still be able to use the DATA partition on lubuntu without losing the hibernated data on windows, which is on windows system partition.
The problem is probably due to an incorrect reset of the graphic card/device after suspend and/or resume. In these cases, often performing the suspend/resume from a Virtual Console helps. (In the link above, you have detailed instructions).
Also had a similar problem with Qiana Mint. The best I could manage after following many of the above was one hibernation - the second would freeze. var/log/syslog yielded an error on restart concerning "rsyslogd-2039". Here's the link http://kb.monitorware.com/kbeventdb-detail-id-6904.html Following that method produced different problems. I finally ...
Go into terminal and type the following, sudo killall NetworkManager If that doesn't work, create a file named /etc/pm/sleep.d/10_resume_network containing #!/bin/sh #Tell Network Manager that resume was successful case "$1" in thaw) nmcli nm sleep false ;; esac Then chmod 775 /etc/pm/sleep.d/10_resume_network. I hope I found ...
I've had the very same problem on my Lenovo Yoga. I've unchecked the 'Configure new displays when connected' checkbox at display settings dialog. Give it a try - I hope it helps.
Top 50 recent answers are included