Closed t3e closed 3 months ago
Ok I think it's clear now what the problem is: If before the suspend both timeouts have passed and no user interaction follows after the wakeup, then there isn't another timeout event after the after_resume event if no user interaction follows. I think I could fix this manually with some shell script but maybe it would be nice if the timeout timers would be reset automatically after every resume from suspend mode.
I've changed my mind, I think it makes more sense the way it works now.
I've noticed a problem when I'm waking a system from sleep mode over network with a WOL package. Afterwards the timeout events no longer work (but resume still does for some reason).
timeout1 before_sleep resume1 after_resume timeout1 before_sleep
-> wakeup via WOL
after_resume resume1
(no more timeout events...)
This only happens with wake on LAN!