[bisq-network/bisq] Transaction stuck, can't open mediation because "deposit transaction" is missing (#4872)
polaris1205
notifications at github.com
Wed Dec 2 03:30:02 CET 2020
<!--
SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
If you have a support request, please join #support on Bisq's
Keybase team at https://keybase.io/team/Bisq
-->
### Description
I have a transaction that has been stuck since November 7, and when I try to open a support ticket, this is the error message it shows (See attached image below).
Also note, the trade period is stuck at 4 days, it doesn't count down.
#### Version
<!-- commit id or version number -->
1.4.2 when the error occured.
Currently running 1.5.0
### Steps to reproduce
<!--if you can reliably reproduce the bug, list the steps here -->
I don't know how to reproduce this, but this is what happened:
1) When I initially took the offer to buy, BISQ crashed suddenly. Afterwards, an error message prevented me from initiating the application.
2) Upon reseacrch, I realized my wallet got corrupted, so I deleted the wallet file, reopened BISQ, and finally used the seed to restore.
3) My wallet balance now showed 0 BTC (I had a balance since I transferred BTC for the deposit).
4) I tried to do an SPV re-sync, but after leaving it on for days, I gave up. (My processor was also running very hot/ max capacity)
5) I imported the wallet seed into Electrum, and was able to salvage the BTC I had transferred. But the transaction on BISQ has remained stuck ever since, and the seller still has his BTC locked in there.
### Expected behaviour
<!--description of the expected behavior -->
### Actual behaviour
<!-- explain what happened instead of the expected behaviour -->
### Screenshots
<!--Screenshots if gui related, drag and drop to add to the issue -->
![Capture](https://user-images.githubusercontent.com/66457627/100819738-bd9e6300-341a-11eb-8adb-d839d41191ad.JPG)
#### Device or machine
<!-- device/machine used, operating system -->
HP-Envy-15 2040nr (2012)
Windows 7
#### Additional info
<!-- Additional information useful for debugging (e.g. logs) -->
--
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/4872
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201201/a7b6844a/attachment.htm>
More information about the bisq-github
mailing list