[bisq-network/bisq] "Deactivating open offer due to mempool validation" does not produce any GUI explanation (Issue #6127)

[JeremyRand]

### Description

The "Deactivating open offer due to mempool validation" error (introduced by https://github.com/bisq-network/bisq/pull/5160 ) does not result in any GUI prompt telling the user what's wrong.  The user must check the log file to gain any understanding of why their offer spontaneously disabled itself (and the GUI does not instruct the user to check the log).  This is a UX issue.

#### Version

v1.8.4.

### Steps to reproduce

1. Have an open offer that fails mempool validation.
2. Enable it by clicking the Status toggle.
3. Wait a few minutes.

### Expected behaviour

When the offer disables itself, the GUI should display a message somewhere (perhaps as an icon with popup next to the offer) that explains why the offer was disabled, and preferably give some suggestions on how to fix it.

### Actual behaviour

No indication in the GUI is given as to what's wrong.  The offer just disables itself without explanation.  User has to think of checking the logs to figure out what happened.

### Screenshots

N/A (issue is lack of GUI, not a bug in GUI that exists).

#### Device or machine

Haswell i7, Whonix 16 inside Qubes 4.1.

#### Additional info

N/A.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/6127
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/issues/6127 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220401/315a4ada/attachment.htm>