Marty Oehme
fd20fb2576
Previously, swayidle would wait for each command to be finished before executing the next which, with lockscreen running in the foreground, would not happen until it was unlocked again. The results were a working lockscreen after the timeout, but nothing else happening and suspend mode only being engaged *as soon as* the lockscreen was disabled (i.e. when you want to use the PC again). This removes swayidle's waiting for commands to finish and instead simply go on to the next timeout when the time is right and should thus fix the issue. |
||
---|---|---|
.. | ||
init |