Walletwasabi: Can't load any wallets until RuntimeParams.json is deleted

[4NobleTruths]

General Description

Almost never can open the wallet without deleting RuntimeParams.json file first.
If I don't, wasabi just says "Loading", and clicking on any of the wallets to load doesn't even select them.
Certainly stays like that for hours, if not indefinitely.
Similar to
https://github.com/zkSNACKs/WalletWasabi/issues/3668

How To Reproduce?

1. Open wasabi, and see that it doesn't load any wallets or respond in any way.
2. Close wasabi, which it does
3. Delete RuntimeParams.json file
4. Open wasabi again, and it works as intended.

Operating System

Debian 9

Logs

Last log entry that is not info is:

WARNING Program (80) System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (The peer has been disconnected)
---> System.OperationCanceledException: The peer has been disconnected
--- End of inner exception stack trace ---

Closes normally with:

INFO Program (61) Wasabi GUI stopped gracefully

Wasabi Version

1.1.11.1
Downloaded from
https://github.com/zkSNACKs/WalletWasabi/releases/download/v1.1.11.1/Wasabi-1.1.11.1.deb
with the verification checks.

[MaxHillebrand]

Can't reproduce.

Can you please send more of the logs?

[4NobleTruths]

Thanks. I understand that only I can reproduce it.
Probably not a good idea to be sending logs from such apps around.
I'll just wait and hope it fixes itself with new versions some day.

[yahiheb]

@4NobleTruths A new version should be released in the next days.

[lontivero]

We have seen this problem before happening randomly in users. We have changed things and never heard about it again. This is the first time I know about someone who suffers this consistently. @4NobleTruths can remove all the privacy damaging data from the logs and share it here, that would help. We would prefer to keep this issue opened anyway.

[4NobleTruths]

@4NobleTruths A new version should be released in the next days.

New version worked as it should first time. Next start, it's back to OP.

[molnard]

Hi there,
So is it resolved?

[lontivero]

No, it is not. The problem is that without any information it is impossible to reproduce.