Unable to start, password prompt stuck in the Taskbar

[ghost]

Description

Bisq was unable to be started as the password prompt was stuck in the Taskbar.

Version

1.9.2.

Steps to reproduce

Unknown

Expected behaviour

Password should be able to be entered in order for the Bisq app to startup.

Actual behaviour

Bisq app remained in limbo, mediation and arbitration messages were not received and as a result the Buyer lost their security deposit. When the password issue was finally resolved and Bisq app started, there was no record of what happened in Mediation and Arbitration as the messages were never received.

Device or machine

Windows 10.

Additional info

User (buyer) said "i did something with my computer and could not open bisq app ...the password prompt was stuck in the taskbar....and i instqall another bisq to the up-date version i try a couple of things to fix....and the arbitror chat wasn't there on ther first instance of my bisq......dont know what happen there but i restore everything and the chat pop up on july 11 after 7 days....but in my head the dispute was done"

Logs analysis:

What I'm seeing is a gap between Jun 23 - Jul 09 and during that gap the app is present (writing to the log) but not started up, (presumably because they were unable to enter their password going from what you quoted above). There is no logging of that trade during that time window. However some mailbox messages and a MediatedPayoutTxSignatureMessage were received on Jun 29: the app does not associate them with the trade, presumably because it is not started up correctly. From Jul 09 onwards the trade begins to be mentioned again, and the user sends a chat message to the dispute agent and receives a response.

I've verified this scenario in regtest, if one side of the trade does not enter the wallet password, dispute messages are ignored because the app is essentially not started up and has no knowledge of trades in progress. When they finally do enter their password, its as if their trade had been frozen in time since the last time the app was successfully used.

Conclusion

The Bisq app needs to start up in order to receive P2P network messages. The stuck password prompt prevented that. More investigation needs to be done to find why on Windows 10 the password prompt got stuck as reported by the user.

[ghost]

💡 I think it probably was this issue: #5648 with the solution for Windows 10 to make the Bisq shortcut "RUN: Maximized"

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.