k9ert

See also: https://github.com/layer2tech/mercury-wallet/issues/322#issuecomment-1334990429 relevant comment: > For TOR build used for this https://github.com/cretz/tor-static > > For windows, I downloaded the Windows Expert Bundle from here: > https://www.torproject.org/download/tor/

I was not able to verify, that this fixes the bug. So this should work without a new HWI-version, right? So as a workaround, download the https://trezor.io/trezor-suite and disable passphrase.

I think a double-check should not be needed. Next step would be to wait for the release. Hopefully we'll see that at the end of the month as Andrew said...

Needs new hwi-version: https://github.com/bitcoin-core/HWI/releases/tag/2.2.0

The dependency has been updated in [hwi 2.2.1](https://github.com/bitcoin-core/HWI/blame/2.2.1/pyproject.toml). Removing the waiting_for_upstream label.

Yes, this is expected behaviour. You won't realise until you (re-) start your specter which is usually not the case for specter running in node-implementations. However, this should be quick...

Sorry for the late reply. As specter is, in theory, a multi-node application, this could be due to all nodes having `"autodetect": false,`. So the question is why and how...

Unfortunately, the language is only stored in the session but not persisted anywhere. So rebooting specter falls back to the default language which is set in the browser. See here...

Seems to be in since [1.0.22](https://github.com/Blockstream/Jade/releases/tag/1.0.22)

I don't think @bitcoinheiro issue is directly related as this would need to be implemented in [Specter-DIY ](https://github.com/cryptoadvance/specter-diy) to work for him.