etcher: Error: (0 , h.requestMetadata) is not a function
- Etcher version: 1.18.13 - 1.19.3
- Operating system and architecture: NixOS, x86_64-linux
- Image flashed: Arbitrary image
- What do you think should have happened: Image selected successfully, being able to select target
- What happened: Can’t select any image
- Do you see any meaningful error information in the DevTools? No, same error as above.
In Nixpkgs we package Etcher on the basis of the official deb. The procedure no longer works as of 1.18.13.
Likely a continuation of #4138. Probably that issue should be reopened? @dfunckt
About this issue
- Original URL
- State: closed
- Created 6 months ago
- Reactions: 14
- Comments: 52 (2 by maintainers)
Like you but I’m using ArchLinux 😦
On arch linux, installed https://aur.archlinux.org/packages/etcher-bin from the AUR and it works, https://aur.archlinux.org/packages/balena-etcher shows the error. For what is worth, the etcher-bin pkg was last updated 2023-07-15, while balena-etcher was updated 2023-12-20.
@polsvoice @TerrorBite @myxor @gaby64 @wegank @lh1207 @GarlandKey @ShalokShalom @pamo22 @arbaes Looks like they finally fixed it with this commit > https://github.com/balena-io/etcher/commit/2dfa795129e287f887b9ea02f2eca717575d27ac
Same issue on Ubuntu 22.04 with X11 using balenaEtcher-1.19.3-x64.AppImage but no error when using balenaEtcher-1.18.11-x64.AppImage
Also having this issue on Manjaro
Thanks!!! etcher-bin is worked for me
Archlinux, Is this same problem?
this has been an issue for 5 months with the balena-etcher aur. upon removing balena-etcher and replacing with etcher-bin, the issue is resolved.
wtf, this is still not fixed?
OS: Fedora 39 pkg: balena-etcher-1.19.4-1.x86_64.rpm
Looking at the inspector the error is thrown in the
source-selectorcomponent here… https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/components/source-selector/source-selector.tsx#L425requestMetadatawhich is imported fromappis stillundefined.https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/app.ts#L139-L157
Since
requestMetadatais initially defined asundefinedthere needs to be an additional check inselectSourceto know thatrequestMetadatahas been defined. It appears the only way to know this is listening for the emittedscanevent, but I didn’t deep dive on a solution.I use archlinux ,balenaEtcher-1.18.8-x64.AppImage can use
It looks like the move to building with electron-forge causes build issues on Arch, and this is why the AUR package is still on version 1.18.
Can we close this? @wegank
@ShalokShalom I might base my fork on the 1.18.x branch instead.
@aethernet @dfunckt @klutchell Is someone going to look at this? I’ve been waiting 2 months now. It prevents making working builds on Linux and Windows. I have a fork that still supports Windows 7, and this is blocking me from doing any more work on it. pkg or yao-pkg is not bundling all the native modules into etcher-util properly. I say yao-pkg because I tried @aethernet two patches related to this (and updating to Node 20, with no luck). Running pkg with --debug, the only thing I see is it complains about no prebuilt binaries. But shouldn’t it be building from source with electron-rebuild anyway?
Hello, same error here:
Same on Arch on both x11 and wayland, installed with yay from aur (since people above were talking abt wayland)
AppImage works fine
Getting the same on Fedora 39 with version v1.19.3. Tried both RPM and AppImage formats. Same result. -1706048290684.log
Thanks for the reports guys. This basically means the sub-process
etcher-utilscould not be spawned properly (or is not yet ready). There might be more infos in the debug console. Can you check what it says ( Ctrl + Shift + I should open it) ?Same problem here with EndeavourOS.