[bisq-network/bisq] AvoidStandbyService suspend inhibitors left running after v1.3.2 test sessions (#4170)

[Stan]

### Description

There some Bisq shutdown scenarios that leave orphaned avoid standby service mode inhibitors.
#### Version

1.3.2

### Steps to reproduce

1. Build v1.3.2 on a GNOME, Ubnutu 18 desktop
2. Start seednode, arbitrator, alice and bob instances in regtest mode after setting up dev / dao test env as per [dao-setup.md](https://github.com/bisq-network/bisq/blob/master/docs/dao-setup.md)
3. Perform wallet recovery tests as per [ontestpad](https://bisq.ontestpad.com/script/187#//), for Alice and Bob instances
4. When all done, check for orphaned gnome session manager inhibitors:
    
        echo "All org.gnome.SessionManager Inhibitors..." 
        dbus-send --session --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitors

         Result array is not empty:

          array [
                 object path "/org/gnome/SessionManager/Inhibitor12"
                 object path "/org/gnome/SessionManager/Inhibitor13"
                 object path "/org/gnome/SessionManager/Inhibitor14"
                 ...
            ]

### Expected behaviour

Result array is empty; there are no orphaned sleep inhibitors:

          array [
            ]

### Actual behaviour


Result array is not empty;  there are orphaned sleep inhibitors:

          array [
                 object path "/org/gnome/SessionManager/Inhibitor12"
                 object path "/org/gnome/SessionManager/Inhibitor13"
                 object path "/org/gnome/SessionManager/Inhibitor14"
                 ...
            ]

### Screenshots

<!--Screenshots if gui related, drag and drop to add to the issue -->

#### Device or machine

Linux / Ubuntu 18



#### Additional info

One scenario probably causing this is when desktop is automatically shut down after recovering wallet from seed, and AvoidStandbyService.shutdown() is not invoked.  

The bug is noticed by user when logging out of linux session, and he sees a "processes still running" warning (these are the orphaned inhibitors), but this does not block session logout, and inhibitors are shut down if the user clicks 'OK', shut down.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4170
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200414/1ce51f69/attachment.html>