elementary OS Stack Exchange is a question and answer site for developers and users of elementary OS and applications. It only takes a minute to sign up.
Sign up to join this community
My PC has dual boot Mint (Debian used for several years) and Elementary. Elementary suspends fine, but unlike Mint, on resume the HD spins up but screen remains blank. I have to use the Power button to force shutdown.
As an aside, when using Firefox, and menu/deskcut, there is no deskcut placed in the desktop folder??
Thanks vm for any help.
If you are using nVidia graphics, check if you are using the proprietary drivers and if not, enable them. To do that open Slingshot, type in "Additional Drivers" and select it from the opening dialog.
If your laptop has an nVidia graphics card, it may be the open source graphics driver causing the problem. The open source graphics driver has some power management issues on some laptops. Try switching to the closed source drivers with the Hardware drivers tool from the menu:
Answer to: "Laptop does not wake up after sleep" by StackExchange user jr0cket
We are supposed not to recommend the intallation of third party ppas, however this makes the configuration of suspend/resume so much more easy (actually, just a tick in a box) that I thought it would be worthy to post.
Install netext73, which is a software from a Romanian group who sells custom kernels for linux. You don't have to buy their kernels in order to use the fix for hibernation. In reality, you could as well uninstall it after the whole process and you would be fine.
For its installation:
sudo apt-add-repository ppa:netext/netext73
sudo apt-get update
sudo apt-get install netext73
And launch netext73:
netext73
Go through the first installation.
Check Hibernate in the optimizer.
To fix the black screen on resume, just install the proprietary video driver and blacklist: nouveau (/etc/modprobe.d/blacklist.conf)
After doing this, resume should work properly.
Switch your TTY (CTRL-ALT-F1) and try running sudo killall lightdm. It should drop you back to the login screen and you should be able to log in as normal. This sounds like a confirmed bug located here
