Walletwasabi: Crash upon trying to export binary PSBT

[21isenough]

General Description
Wasabi Wallet crashes upon trying to export the binary PSBT.

How To Reproduce?

1. Advanced > Build Transaction
2. Build the transaction on click "Build Transaction"
3. Click on "Export Binary PSBT"
4. An additional window opens shortly and then crashes. Closes that new window and the Wasabi Wallet.

Logs
(dotnet:7855): dconf-WARNING **: 14:12:20.889: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=3ac1fc0ec1ed475e87e1a05e1fc224e3 --binary-syntax --close-stderr”: Child process exited with code 1

Operating System
Linux Manjaro
Kernel 4.19.56-1-MANJARO

Wasabi Version
v1.1.6

[MaxHillebrand]

Cannot reproduce on Debian 9.9, for me both the binary PSBT and the final transaction can be broadcasted without issue...

[wundrellama]

I'm having the same issue when I attempt to export the binary PSBT on both the release version 1.1.6 and on a fresh build from the main branch. Running on 5.1.16-arch1-1-ARCH #1 SMP PREEMPT x86_64 GNU/Linux

[MaxHillebrand]

Thanks for letting us know @wundrellama!
To clarify, when exactly does it crash?

1. You click on Export Binary PSBT
2. The file manager pops up and you directly select the SD card, then you click save
3. Or another way

[wundrellama]

It crashes about 3 seconds after I click on Export Binary PSBT. In my case, I never see the file manager.

[molnard]

We have a fallback case here in Wasabi. On any error Wasabi opens a simple Text input to enter the path. The problem is that any error is not given to us by the OP system because Wasabi killed by OS very impolitely.

Unfortunately the log message is now useful for me.

Walk around can be to not use the button but copy/paste the PSBT manually (I am sure you already figured that out, just for the record).

Every solution what comes to my mind would mess up the UI. I think it is a problem with the OP system. Should be fixed there.

[wundrellama]

What about adding a user definable default path to the config.json file?

[molnard]

I don't think it is useful for other users and adds extra complexity. If the path is there we should just save without the possibility to select the path - it is a strange behavior and would generate more issues than it solves.

[nopara73]

Fixed. (ToDo: insert @danwalmsley's PR here.)