repowerd, or some other process that acquires logind suspend inhibitions, could be involved in this. It's easy to find out if this is the case by running:
$ systemd-inhibit
and checking if any inhibitions with parameters What:sleep Mode:block are active. Note that repowerd acquiring such an inhibition just means that another program has requested a suspend inhibition from repowerd.
In any case, as discussed in bug 1668596, repowerd will soon stop acquiring logind suspend inhibitions.
repowerd, or some other process that acquires logind suspend inhibitions, could be involved in this. It's easy to find out if this is the case by running:
$ systemd-inhibit
and checking if any inhibitions with parameters What:sleep Mode:block are active. Note that repowerd acquiring such an inhibition just means that another program has requested a suspend inhibition from repowerd.
In any case, as discussed in bug 1668596, repowerd will soon stop acquiring logind suspend inhibitions.