When a timeout for a specific power state creates a lock file, and then another timeout of the same power state also creates a lock file, the resumeScript of the preceding timeouts is not run, and lock files from those timeouts are not cleared.
For example, take the following timeouts when on battery:
- A. Dim the screen after 120 seconds.
- B. Turn off the screen after 240 seconds.
- C. Suspend after 300 seconds.
Once timeout C is run, upon the resumeScript, the resume scripts for A and B are not run. This means that the lock files and/or state they affect is not restored upon completion of C.
When a timeout for a specific power state creates a lock file, and then another timeout of the same power state also creates a lock file, the
resumeScriptof the preceding timeouts is not run, and lock files from those timeouts are not cleared.For example, take the following timeouts when on battery:
Once timeout
Cis run, upon theresumeScript, the resume scripts forAandBare not run. This means that the lock files and/or state they affect is not restored upon completion ofC.