<p></p>
<h3>Description</h3>
<p>There some Bisq shutdown scenarios that leave orphaned avoid standby service mode inhibitors.</p>
<h4>Version</h4>
<p>1.3.2</p>
<h3>Steps to reproduce</h3>
<ol>
<li>
<p>Build v1.3.2 on a GNOME, Ubnutu 18 desktop</p>
</li>
<li>
<p>Start seednode, arbitrator, alice and bob instances in regtest mode after setting up dev / dao test env as per <a href="https://github.com/bisq-network/bisq/blob/master/docs/dao-setup.md">dao-setup.md</a></p>
</li>
<li>
<p>Perform wallet recovery tests as per <a href="https://bisq.ontestpad.com/script/187#//" rel="nofollow">ontestpad</a>, for Alice and Bob instances</p>
</li>
<li>
<p>When all done, check for orphaned gnome session manager inhibitors:</p>
<pre><code> 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"
          ...
     ]
</code></pre>
</li>
</ol>
<h3>Expected behaviour</h3>
<p>Result array is empty; there are no orphaned sleep inhibitors:</p>
<pre><code>      array [
        ]
</code></pre>
<h3>Actual behaviour</h3>
<p>Result array is not empty;  there are orphaned sleep inhibitors:</p>
<pre><code>      array [
             object path "/org/gnome/SessionManager/Inhibitor12"
             object path "/org/gnome/SessionManager/Inhibitor13"
             object path "/org/gnome/SessionManager/Inhibitor14"
             ...
        ]
</code></pre>
<h3>Screenshots</h3>

<h4>Device or machine</h4>
<p>Linux / Ubuntu 18</p>
<h4>Additional info</h4>
<p>One scenario probably causing this is when desktop is automatically shut down after recovering wallet from seed, and AvoidStandbyService.shutdown() is not invoked.</p>
<p>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.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/4170">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNS6M6H4DGFVTP26OYTRMSKXNANCNFSM4MH5CCNQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNRTR462WWBZREKAJADRMSKXNA5CNFSM4MH5CCN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4I57D5PA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/4170",
"url": "https://github.com/bisq-network/bisq/issues/4170",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>