Recently my system has been refusing to suspend. How can I debug? (I've recently installed expressvpn, could this be the issue?) Here's what the log says:
Apr 18 02:30:01 nbecker2 systemd[1]: Started Suspend. Apr 18 02:30:01 nbecker2 systemd[1]: sleep.target: Unit not needed anymore. Stopping. Apr 18 02:30:01 nbecker2 systemd[1]: Stopped target Sleep. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Bound to unit systemd- suspend.service, but unit isn't active. Apr 18 02:30:01 nbecker2 systemd[1]: Dependency failed for Suspend. Apr 18 02:30:01 nbecker2 systemd-logind[718]: Operation 'sleep' finished. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
2018-04-18 8:58 GMT+02:00, Neal Becker ndbecker2@gmail.com:
Recently my system has been refusing to suspend. How can I debug? (I've recently installed expressvpn, could this be the issue?) Here's what the log says:
Apr 18 02:30:01 nbecker2 systemd[1]: Started Suspend. Apr 18 02:30:01 nbecker2 systemd[1]: sleep.target: Unit not needed anymore.
Stopping. Apr 18 02:30:01 nbecker2 systemd[1]: Stopped target Sleep. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Bound to unit systemd- suspend.service, but unit isn't active. Apr 18 02:30:01 nbecker2 systemd[1]: Dependency failed for Suspend. Apr 18 02:30:01 nbecker2 systemd-logind[718]: Operation 'sleep' finished. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
FWIW, I see similar messages in the logs, but suspend works...
Andras Simon wrote:
2018-04-18 8:58 GMT+02:00, Neal Becker ndbecker2@gmail.com:
Recently my system has been refusing to suspend. How can I debug? (I've recently installed expressvpn, could this be the issue?) Here's what the log says:
Apr 18 02:30:01 nbecker2 systemd[1]: Started Suspend. Apr 18 02:30:01 nbecker2 systemd[1]: sleep.target: Unit not needed anymore.
Stopping. Apr 18 02:30:01 nbecker2 systemd[1]: Stopped target Sleep. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Bound to unit systemd- suspend.service, but unit isn't active. Apr 18 02:30:01 nbecker2 systemd[1]: Dependency failed for Suspend. Apr 18 02:30:01 nbecker2 systemd-logind[718]: Operation 'sleep' finished. Apr 18 02:30:01 nbecker2 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
FWIW, I see similar messages in the logs, but suspend works...
Perhaps the messages are not related to the suspend issue. But the symptoms are very strange. The laptop appears to suspend (power light changes from on to flashing), but at a random time later (seconds to minutes later), it wakes itself up again! Only thing I could think of is WOL, but it's not connected to wired enet.
Allegedly, on or about 19 April 2018, Neal Becker sent:
Perhaps the messages are not related to the suspend issue. But the symptoms are very strange. The laptop appears to suspend (power light changes from on to flashing), but at a random time later (seconds to minutes later), it wakes itself up again! Only thing I could think of is WOL, but it's not connected to wired enet.
Other BIOS wake-up methods? Wake on mouse, perhaps, if a slight bump has made the mouse move.
On 04/19/18 20:50, Tim via users wrote:
Allegedly, on or about 19 April 2018, Neal Becker sent:
Perhaps the messages are not related to the suspend issue. But the symptoms are very strange. The laptop appears to suspend (power light changes from on to flashing), but at a random time later (seconds to minutes later), it wakes itself up again! Only thing I could think of is WOL, but it's not connected to wired enet.
Other BIOS wake-up methods? Wake on mouse, perhaps, if a slight bump has made the mouse move.
Additionally:
some BIOSes wake up on Network events (if the computer is attached to the lan).
Joachim Backes