Comment 4 for bug 1668596

The problem is that the program with dbus address :1.219 requested the "active" state for the system, i.e. it has disallowed suspend.

The program first requests the "active" state and then clears it:

2017-02-28T09:50:13.018142+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1)
2017-02-28T09:50:13.030120+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1) => 1
2017-02-28T09:50:14.484885+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_clearSysState(:1.219,1)

And ~10 seconds later it requests the "active" state again and never clears it after that:

2017-02-28T09:50:25.021176+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1)
2017-02-28T09:50:25.030948+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1) => 2