Electrum 4.4 Relased

[ghost43]

3.
https://loyce.club/other/settings3.png

What in the world does "Download missing data" do?

There is a tooltip if you mouse-over. It's mostly useful where the inputs are external (not owned by the wallet): if the parent txs are missing, the tx fee cannot be calculated, and e.g. the address corresponding to the input cannot be shown. If enabled, if the parent txs are missing, they are downloaded from the electrum server, and the otherwise missing fields can then be shown.

[1714590820]

1714590820

[PawGo]

And just a few days after not well received 4.4, we have a new hotfix release:

Code:

# Release 4.4.1 (April 27, 2023)
 * Qt GUI:
   - fix sweeping (#8340)
   - fix send tab input_qr_from_camera (#8342)
   - fix crash reporter showing if send fails on typical errors (#8312)
   - bumpfee: disallow targeting an abs fee. only allow feerate (#8318)
 * QML GUI:
   - fix offline-signing or co-signing pre-segwit txs (#8319)
   - add option to show onchain address in ReceiveDetailsDialog (#8331)
   - fix strings unique to QML did not get localized/translated (#8323)
   - allow paying bip21 uri onchain that has both onchain and bolt11
     if we cannot pay on LN (#8334, 312e50e9)
   - virtual keyboard: make buttons somewhat larger (75e65c5c)
   - fix(?) Android crash with some OS-accessibility settings (#8344)
   - fix channelopener.connectStr qr scan popping under (#8335)
   - fix restoring from old mpk (watchonly for "old" seeds) (#8356)
 * libsecp256k1: add runtime support for 0.3.x, bump bundled to 0.3.1
 * forbid paying to "http:" lnurls (enforce https or .onion) (1b5c7d46)
 * fix wallet.bump_fee "decrease payment" erroring on too high target
   fee rate (#8316)
 * fix performance regressions in tx logic (ee521545, 910832c1)
 * fix "recursion depth exceeded" for utxo privacy analysis (#8315)

Good to see some fixes, but of course it is not an answer for complaints about GUI changes.

[blue Snow]

And just a few days after not well received 4.4, we have a new hotfix release:

I got this error (Can't bump a fee) after updating, I don't know the exact problem, I was enabled RBF.



I don't know what mean No Suitable Output, when I look in exlorer I got Opted in on RBF notes

[pooya87]

I don't know what mean No Suitable Output, when I look in exlorer I got Opted in on RBF notes

Generally speaking this problem occurs when the software can not find any output (the address(es) you pay to) to deduct the extra fees from. It could be because none of them are a change address that it can detect or if deducting it from the change it detected would make it too small.

[nc50lc]

I don't know what mean No Suitable Output, when I look in exlorer I got Opted in on RBF notes

Probably not related to the update.
It means that it can't find any UTXO to add in order to fulfill the additional fee.
Most likely caused by using "max" amount and having no change output.

Your selected "method" is "Preserve Payment" which is set to keep the recipient's amount intact;
So, it'll have to provide additional input if your transaction doesn't have a change.

Selecting the other option should work in your case but it'll decrease the to-be-sent amount of bitcoins.

[Charles-Tim]

   - When you click on the Receive button, it only shows a qr code, it doesn't show the address in plain text which may be dangerous in case your device is infected with the clipboard malware.

I have noticed this in some previous versions. Not dangerous because if you paste the address where you want to use it, you will see the address.

   - When you click on the Send button, it immediately starts the camera to scan the address qr code. There is no option to enter the address manually. You need to have the address already copied on the clipboard then you can paste it. Besides, there is no option to edit the address after pasting it.

I like this very much. I wanted to screenshot it but I was unable to do that because the page is rejecting screenshot. If you want to send, just copy the address and go to Electrum mobile and click on 'send' to paste it, it will immediately display the address for you to see. It even display the address clearly and  in full.

Also, on the Send tab, when tapping the Max button, the amount field will not display the max amount to send. You need to click on Pay to see it on the next screen. At first, I thought it doesn't work until I clicked Pay.

This is only what I saw to be very valid, but which is not an issue at all. Once you click on max, the 'pay' button will change obviously and noticably and you will be able to proceed to broadcast the transaction if you click on pay.

[Lucius]

I upgraded the Android version to 4.4.0 and every time I tried to send a transaction Electrum would just crash, so I upgraded to the last possible version 4.4.1 and now after I click on the Pay button I get a screen with a QR code and two messages, the first of which reads :

Transaction created and partially signed by this wallet. Present this QR code to the next co-signer.

The second message is some kind of additional warning, but this version of Electrum doesn't allow taking a screen sample. I note that this is not a multi-sig or 2FA wallet, and it was created with the Android version of Electrum.

[ghost43]

I upgraded the Android version to 4.4.0 and every time I tried to send a transaction Electrum would just crash, so I upgraded to the last possible version 4.4.1 and now after I click on the Pay button I get a screen with a QR code and two messages, the first of which reads :

Transaction created and partially signed by this wallet. Present this QR code to the next co-signer.

[...] I note that this is not a multi-sig or 2FA wallet, and it was created with the Android version of Electrum.

Sounds like you have a pre-segwit watchonly wallet. The reason you are shown a QR code after creating the tx is because you cannot complete it with just that wallet. As you say it is not multisig or 2FA, I guess it must be watchonly.
The piece of information that in 4.4.0 it would just crash also reaffirms this: see changelog item

- fix offline-signing or co-signing pre-segwit txs (#8319)

[Lucius]

@ghost43, I'm pretty sure I don't have a watch-only wallet and I didn't have any problems in previous versions. I solved the problem by going back to version 4.3.4 and then I was able to make a transaction without any problems. I don't know what the developers wanted to achieve with the new versions, but I personally don't like it and if they continue like this, Electrum will no longer be my first choice when it comes to hot wallets and smartphones.

[ghost43]

@ghost43, I'm pretty sure I don't have a watch-only wallet

Well, what kind of wallet do you have? The more details you can give, the better. (no secret keys, etc. though)
If you go into "Wallet details", what icons/badges do you see at the top? (e.g. for one wallet of mine I see "standard", "p2wpkh", "HD", "Encrypted", "Lightning", "Seed")
Going back to an old version is just a temporary workaround. If you would like your problem to get fixed, please help in reproducing it. (and ideally open bug reports on github, it is difficult to keep track of reports across multiple places...)

EDIT: Ah ok, I guess this must be https://github.com/spesmilo/electrum/issues/8374
The issue triggers for wallets that have encrypted keystore but not encrypted storage. This can only be the case on wallets created with old versions of kivy, where the password hasn't been unified.

[Lucius]

It is a standard wallet, and the matter is similar to the link you provide - although I had several wallets, some of which were created with imported private keys. The wallet that was the problem was default_wallet, and the problem was solved by going back to version 4.3.4 on the same device (Android 10 or 11 - not sure).

Just to clarify that my problem is similar, but that user on github and I are not the same person.

I see that version 4.4.2 is 90% complete and that this problem should also be solved, we just have to wait -> https://github.com/spesmilo/electrum/milestones

[PawGo]

I see that version 4.4.2 is 90% complete and that this problem should also be solved, we just have to wait -> https://github.com/spesmilo/electrum/milestones

Version 4.4.2 has been released, could you confirm your problem is solved?

Looks like 4.4 was intended to be a major release, as changes are not trivial, but it caused many problems. On the other hand we have a 2nd patch just in 2 weeks, that's good we do not need to wait months for updates.

Code:

# Release 4.4.2 (May 4, 2023)
 * Qt GUI:
   - fix undefined var check in swap_dialog (#8341)
   - really fix "recursion depth exceeded" for utxo privacy analysis (#8315)
 * QML GUI:
   - fix signing txs for 2fa wallets (#8368)
   - fix for wallets with encrypted-keystore but unencrypted-storage (#8374)
   - properly delete wizard components after use (#8357)
   - avoid entering loadWallet if daemon is already busy loading (#8355)
   - no auto capitalization on import and master key text fields (5600375d)
   - remove Qt virtual keyboard and add Seedkeyboard for seed entry (#8371, #8352)
   - add runtime toggling of android SECURE_FLAG, to allow screenshots (#8351)
   - restrict cases where server is shown "lagging" (53d61c01)
 * fix hardened char "h" vs "'" needed for some hw wallets (#8364, 499f5153)
 * fix digitalbitbox(1) support (22b8c4e3)
 * fix wrong type for "history_rates" config option (#8367)
 * fix issues with wallet.get_tx_parents (a1bfea61, 56fa8325)

[Lucius]

Version 4.4.2 has been released, could you confirm your problem is solved?

Thanks for the info, I just checked in the PlayStore and I see that the new version is available, but right now I can't check if the problem still exists because my wallet is completely empty, and considering the current fees, I'll wait a bit before testing

Anyway, I'll try the new version ASAP and come back with feedback.