trezor: strange behaviour with 2.1.1: cannot sign, send transactions, getting "watch only mode" albeit pin and passphrase are asked

[molecular]

Using trezor firmware 1.3.3
Not sure which python-trezor version I'm using. setup.py contains string "version='0.6.3'"

Here's what I do and what happens:

• replug trezor
• start electrum
• getting PIN entry dialog, entering correct pin
• immediately getting popups 1.) trezor device not detected, continuing in watch-only mode and 2.) please enter your trezor passphrase
• entering correct trezor passphrase
• closing popup "trezor device not detected" by clicking "ok"

now trying to sign (this problem occurs with 2.0.4, also, but it works in 2.0b3)

• tools -> sign/verify -> enter address and message, click "sign"
• getting popup "Got <class 'trezorlib.messages_pb2.PublicKey'>, expected (<class 'trezorlib.messages_pb2.Success'>,)

trying "send"

• "send" tab: entering "pay to", description, amount, click "send"
• confirm fee
• getting "transaction popup" (have "show transaction before broadcast" enabled) without a "broadcast button". only option is to "close" or "save" transaction. I "close"

no messages on the console during everything above

[molecular]

I tried with another trezor device that has an older firmware.

Except that PIN is not asked on startup of electrum, behaviour is the same:

• start electrum
• passphrase is asked
• popup "trezor not detected, watch-only"

[molecular]

I went back to 2.0b3 and it works fine (tested sending) with the old firmware (not sure which version it is, don't know how to check).

With the 1.3.3 firmware I had a problem with an empty popup first, but when I wanted to document this, it worked (tested signing)

So 2.0b3 seems to work well (I've used this the last month or so anyway) with both older and 1.3.3 firmware

[molecular]

I tried signing in 2.0.4 with firmware 1.3.3, it fails with the popup "Got <class 'trezorlib.messages_pb2.PublicKey'>, expected (<class 'trezorlib.messages_pb2.Success'>,)". Signing works in 2.0b3 with same firmware.

[ecdsa]

thanks for all the details. I will have a look this week end

[molecular]

cool! Thanks for all the great work.

[chrisrico]

It seems like the fimrware-Electrum version conflicts would be solved by releasing a version of the Trezor plugin per version of the firmware. Just drop the correct version into your plugin folder. Or is it not that easy due to dependencies?

[keo]

same here with fw 1.3.3 and newest plugin / bridge + electrum 2.1.1...

[molecular]

@keo: thanks for confirmation.

@chrisrico: I used the newest python-trezor from github at the time, so unless satoshilabs was slow to sync to newest firmware, that should not have been the issue.

I just pulled python-trezor and there are some changes made since then. There were some changes by slush regarding fw update on April 9th, but I should've had these included at the time of writing OP.

Will recheck soon.

[ecdsa]

@molecular do you still have this issue?

[molecular]

doesn't occur any more like this on master or 2.2

thanks for fixing!