You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though the logs look like swayidle was able to acquire the lock, the lock is released after the system has resumed (look at the timestamps). Moreover, when I run systemd-inhibit (which lists all the inhibitors currently registered), I can't see swayidle
$ systemd-inhibit --list
WHO UID USER PID COMM WHAT WHY MODE
NetworkManager 0 root 445 NetworkManager sleep NetworkManager needs to turn off networks delay
UPower 0 root 27834 upowerd sleep Pause device polling delay
2 inhibitors listed.
I looked at the logind.conf man page and couldn't find any setting that might be relevant to this issue. Any ideas?
The text was updated successfully, but these errors were encountered:
Sway version:
sway version 1.0-beta.2-100-gbb5b168b (Jan 5 2019, branch 'master')
I start
swayidle
with the following commandAnd I get the following log when I run
systemctl suspend
afterwardsEven though the logs look like swayidle was able to acquire the lock, the lock is released after the system has resumed (look at the timestamps). Moreover, when I run
systemd-inhibit
(which lists all the inhibitors currently registered), I can't see swayidleI looked at the
logind.conf
man page and couldn't find any setting that might be relevant to this issue. Any ideas?The text was updated successfully, but these errors were encountered: