You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that on Ubuntu with bitcoind, I run into the following error if the bitcoin GUI has any open windows. Once I dismiss open windows, then lss works fine.
$ ./lss
[2022/09/29 - 12:54:42] INFO Ledger SatStack (lss) v0.12.0 arch=linux amd64 build= commit= runtime=go1.17.13
[2022/09/29 - 12:54:42] INFO Config file detected path=/home/user/.config/Ledger Live/lss.json
[2022/09/29 - 12:54:42] INFO Warming up...
[2022/09/29 - 12:54:42] FATAL Failed to initialize Bus error=failed to load wallet: -4: Wallet file verification failed. SQLiteDatabase: Unable to obtain an exclusive lock on the database, is it being used by another bitcoind?
The error message about the SQLite database wasn't really obvious to me, so my suggestion would be to consider adding this issue as a possibility. ("Do you have any bitcoin windows open? If so, try closing them and re-running lss." or something.)
The text was updated successfully, but these errors were encountered:
Note that on Ubuntu with bitcoind, I run into the following error if the bitcoin GUI has any open windows. Once I dismiss open windows, then lss works fine.
$ ./lss [2022/09/29 - 12:54:42] INFO Ledger SatStack (lss) v0.12.0 arch=linux amd64 build= commit= runtime=go1.17.13 [2022/09/29 - 12:54:42] INFO Config file detected path=/home/user/.config/Ledger Live/lss.json [2022/09/29 - 12:54:42] INFO Warming up... [2022/09/29 - 12:54:42] FATAL Failed to initialize Bus error=failed to load wallet: -4: Wallet file verification failed. SQLiteDatabase: Unable to obtain an exclusive lock on the database, is it being used by another bitcoind?
The error message about the SQLite database wasn't really obvious to me, so my suggestion would be to consider adding this issue as a possibility. ("Do you have any bitcoin windows open? If so, try closing them and re-running lss." or something.)
The text was updated successfully, but these errors were encountered: