Also having this issue on Manjaro

Like you but I'm using ArchLinux :(

I'm getting this with version 1.18.14 on Garuda.

Same for me on ArchLinux.

Getting this on Nobara 38

Was initially trying on Hyprland, which is on Wayland. I download Cinnamon to test and Xorg environment and it worked for me. I used 1.8.13. Is anyone else on Wayland?

I was on wayland

I'm getting this issue on Manjaro with the 1.18.14 version from the AUR and I'm on X11. However, it lools like 1.18.14 released just a couple of days before #4132 was merged, meaning that the fix for #4138 wasn't included in that version. So any Arch/Manjaro issues (@Sargeanthost, @devM7MD, @myxor) should hopefully be fixed when 1.19.x lands on the AUR. Maybe I can try and manually build a 1.19 package and see if it works?

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.

I have the same issue on openSUSE using the RPM and appimage

Same problem here with EndeavourOS.

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

Same issue with balena-etcher-1.19.3-1.x86_64.rpm on Fedora 39

also have same issue with balena-etcher-1.19.3-1.x86_64.rpm on Fedora 39

I use archlinux ,balenaEtcher-1.18.8-x64.AppImage can use

Thanks for the reports guys.
This basically means the sub-process etcher-utils could 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) ?

Thanks for the reports guys. This basically means the sub-process etcher-utils could 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) ?

Getting the same on Fedora 39 with version v1.19.3. Tried both RPM and AppImage formats. Same result.
-1706048290684.log

Same on Arch on both x11 and wayland, installed with yay from aur (since people above were talking abt wayland)

AppImage works fine

Thanks for the reports guys. This basically means the sub-process etcher-utils could 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) ?

node:events:491 Uncaught Error: spawn /usr/lib/balena-etcher/generated/etcher-util ENOENT
    at __node_internal_captureLargerStackTrace (node:internal/errors:490:5)
    at __node_internal_errnoException (node:internal/errors:620:12)
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
(anonymous) @ gui.js:3
gui.js:3 TypeError: requestMetadata is not a function
    at gui.js:278:1759
    at SourceSelector.selectSource (gui.js:278:2719)
    at SourceSelector.openImageSelector (gui.js:278:3117)

Unfortunately console does not have much info

OS: Fedora 39
pkg: balena-etcher-1.19.4-1.x86_64.rpm

Looking at the inspector the error is thrown in the source-selector component here... https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/components/source-selector/source-selector.tsx#L425

requestMetadata which is imported from app is still undefined.

https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/app.ts#L139-L157

Since requestMetadata is initially defined as undefined there needs to be an additional check in selectSource to know that requestMetadata has been defined. It appears the only way to know this is listening for the emitted scan event, but I didn't deep dive on a solution.

still an issue on arch

Archlinux, Is this same problem?

same problem, archlinux

Experiencing the same issue here on Manjaro and Garuda Linux with balena-etcher-2:1.18.14-1.

Just as @Kaiddd commented, I can confirm that the balenaEtcher-1.5.109-x64.AppImage version works fine on both systems.

Same issue here on ElementaryOS and Zorin OS with balenaEtcher-1.19.5-x64.AppImage.
Confirmed that balenaEtcher-1.18.11-x64.AppImage worked on both systems.

Experiencing this problem on my Dell XPS 9520 running Arch Linux. This is with balenaEtcher v1.18.14 from AUR, v1.18.12 AppImage, and v1.19.5 AppImage. Running GNOME 45.4 on Wayland with Intel GPU.

Same on nix home-manager on arch, also if you open it as sudo it doesn't actually give that error however in my setup at least, root etcher doesn't show any graphics, it's just a white screen, but if you know where are the buttons are you can technically do it. Unsure of the safety of this since it's a root action. Not to mention if it gives an error there is no way of knowing it. Btw I'm on Wayland so if you get any graphics on x11 please let me know.

This just caused NixOS to remove the application from the repositories.

See: NixOS/nixpkgs#295853

OS: Arch Linux x86_64
Host: Framework 16 (AMD Ryzen 7040 Series) AJ
Kernel: 6.8.1-arch1-1

Version: balenaEtcher (1.19.5).AppImage

Console log:

index.js:2 /tmp/.mount_balenaScyPgz/usr/lib/balena-etcher/resources/etcher-util
index.js:2 TypeError: (0 , h.requestMetadata) is not a function
    at index.js:140:1418
    at H.selectSource (index.js:140:2212)
    at H.openImageSelector (index.js:140:2543)
(anonymous) @ index.js:2

@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?

Development on Etcher seems to have stopped. Personally, I switched to Ventoy and do not look back at all.

@ShalokShalom I might base my fork on the 1.18.x branch instead.

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.

Thanks!!! etcher-bin is worked for me

wtf, this is still not fixed?

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.

yay -R balena-etcher
yay -S etcher-bin

thanks @lh1207 !

Sadly this remains unfixed. Tested on Fedora Linux 38 (Workstation Edition) with latest rpm.
Etcher used to be a great tool.

Yes I have it on Redhat

Guys, you're using pre-releases that are not marked as production ready for this exact reason.

Having this issue now on MacOS

Guys, you're using pre-releases that are not marked as production ready for this exact reason.

The problem for me at least is that the version available on AUR is an unstable release. Because Arch releases on a rolling basis there's no way for me to peg to the latest stable release other than checking out the source and building myself. So I think the issue is pushing prerelease builds to package repositories.

@polsvoice @TerrorBite @myxor @gaby64 @wegank @lh1207 @GarlandKey @ShalokShalom @pamo22 @arbaes Looks like they finally fixed it with this commit > 2dfa795

@Alex313031 that's great news, thanks for letting us all know 👍

I can confirm this bug indeed fixed with https://github.com/balena-io/etcher/releases/tag/v1.19.16 🥇

Can we close this? @wegank

I still having problems with this error in 1.19.16 i'm running Fedora 40. I've installed the .rpm

I have the same problem on the Hyprland on archlinux i use the appimage.

I have the same problem on the Hyprland on archlinux i use the appimage.

Use yay instead @musicfunfan
#4150 (comment)

problem still present in AppImage, Ubuntu

Can we close this? @wegank

I can't test because of #4150 (comment), but it seems that the same issue persists for AppImage?

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.

yay -R balena-etcher
yay -S etcher-bin

This solved it for me on Manjaro.

issue still exists on balenaEtcher-1.19.16-x64.AppImage

@lh1207 So , i install the appimage available in official etcher site and now is working. The problem is in 1.19.16. The version in the official site is 1.18.11. I think the latest stable version is 1.18.11. So this version we should use.

OS: Windows11 23H2(AMD Ryzen 5600G)
Version: balenaEtcher 1.19.16 and 1.19.17

The ISO image cannot be loaded after selecting it, and destination disk selection is not possible, but version 1.18.11 does not have this problem.

@supercoderlee I thing that the 1.18.11, Is the stable one. This is the one that exist on the site. I think the 1.19* is on Beta or something like that.