Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: (0 , h.requestMetadata) is not a function #4150

Open
wegank opened this issue Dec 21, 2023 · 137 comments
Open

Error: (0 , h.requestMetadata) is not a function #4150

wegank opened this issue Dec 21, 2023 · 137 comments

Comments

@wegank
Copy link

wegank commented Dec 21, 2023

  • 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.
Capture d’écran 2023-12-21 à 18 37 00

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

@Sargeanthost
Copy link

Also having this issue on Manjaro

@devM7MD
Copy link

devM7MD commented Dec 24, 2023

Like you but I'm using ArchLinux :(

@polsvoice
Copy link

I'm getting this with version 1.18.14 on Garuda.

@myxor
Copy link

myxor commented Dec 26, 2023

Same for me on ArchLinux.

@OffsetMonkey538
Copy link

Getting this on Nobara 38

@Sargeanthost
Copy link

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?

@OffsetMonkey538
Copy link

I was on wayland

@TerrorBite
Copy link

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?

@TerrorBite
Copy link

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.

@TobiPeterG
Copy link

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

@LITUATUI
Copy link

LITUATUI commented Jan 8, 2024

Same problem here with EndeavourOS.

@slagathor69
Copy link

slagathor69 commented Jan 14, 2024

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

@shunkica
Copy link

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

@wthubhub
Copy link

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

@eternallfrost
Copy link

This issue does not occur on the appimage version of Etcher

@dualrelax
Copy link

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

scottfurry pushed a commit to scottfurry/FurCaT_Gentoo that referenced this issue Jan 19, 2024
…v1.19.2)"

This reverts commit 3906e49.

Reverting update(v1.19.2 -> v1.18.12)
Upstream Bug #4150 - balena-io/etcher#4150
@aethernet
Copy link
Contributor

aethernet commented Jan 23, 2024

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

@ClassANetwork
Copy link

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

@Kaiddd
Copy link

Kaiddd commented Feb 3, 2024

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

AppImage works fine

@pamo22
Copy link

pamo22 commented Feb 9, 2024

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

@JBlackCat
Copy link

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.

@nath1as
Copy link

nath1as commented Feb 12, 2024

still an issue on arch

@kdh8219
Copy link

kdh8219 commented Feb 14, 2024

Archlinux, Is this same problem?
image

@harperbolic
Copy link

same problem, archlinux

@Niskeletor
Copy link

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.

@wasantosfi
Copy link

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.

@dmophir
Copy link

dmophir commented Feb 19, 2024

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.

@Baku-Stark
Copy link

My problem in Linux Minut
Screenshot 2024-06-23 at 13-20-31 Captura de tela em 2024-06-23 13-18-57 png (imagem PNG 1366 × 768 pixels) - Redimensionada (82%)

@g0r0d3tsky
Copy link

Same on Ubuntu 22.04 with balenaEtcher-1.19.21-x64.AppImage.

@Mr3rf1
Copy link

Mr3rf1 commented Jun 24, 2024

same issue on fedora 39 and balena-etcher-1.19.21-1.x86_64.rpm

@aethernet
Copy link
Contributor

Same on Ubuntu 20.04 with balenaEtcher-1.19.21-x64.AppImage.

It's strange that with all the feedback and trouble, the issue hasn't been tackled yet.

PR welcomes :)

@NikolasPetriti
Copy link

fixed by running as administrator on windows

@Jose-Monteiro
Copy link

Jose-Monteiro commented Jun 26, 2024

Same error here on Fedora 40 with Wayland. Using version 1.18.11 this issue does not appears. The link below is to this version that worked for me.
https://github.com/balena-io/etcher/releases/tag/v1.18.11

@saurabhuja
Copy link

Old version 1.18.11 worked for me. @aethernet Can we rollback recent changes from 1.19.11 to 1.18 ? This is a regression blocker to use it.

@andreidiaconescu
Copy link

andreidiaconescu commented Jul 1, 2024

Hello,
Issue still reproduces running balenaEtcher-1.19.21.Setup.exe on windows 10 and trying to write image for Ubuntu ubuntu-24.04-desktop-amd64.iso
Was able to run balenaEtcher-Setup-1.18.11.exe in the same conditions, and it run fine.

@lazcol
Copy link

lazcol commented Jul 1, 2024

Same error over here with 1.19.19 and 1.19.21 versions. Didn't test other. I am going to unleash dd command. I am running Debian bookworm on a Ryzen 9.
image

@lazcol
Copy link

lazcol commented Jul 1, 2024

Same error over here with 1.19.19 and 1.19.21 versions. Didn't test other. I am going to unleash dd command. I am running Debian bookworm on a Ryzen 9. image

running as sudo ./balenaEtcher-1.19.19-x64.AppImage --no-sandbox it doesn't work either. I tryed because windows people says that it works running as administrator.

@Aracon
Copy link

Aracon commented Jul 3, 2024

balenaEtcher-1.19.21-x64.AppImage on Ubuntu 20.04, same issue

1.18.11 works

@crisdeff
Copy link

crisdeff commented Jul 4, 2024

Having the same issue with Arch Linux 6.4.12-arch1-1 and the version of etcher balenaEtcher-1.19.21-x64.AppImage. I found a way to bypass using the previous version:

https://github.com/balena-io/etcher/releases/tag/v1.18.11

for ubuntu on windows, worked for me thanks

@tojimahammatov
Copy link

Hi all, it happened to me as well but worked when I fixed the issue on my own system, ubuntu 24.04.

I suggest to run the program through terminal, then when you encounter this issue you can see more detailed log in the terminal. In my case it is said that there was no space to write on device. The error message is more descriptive there and might not be belong to balena. Hope it helps.

@carlowisse
Copy link

Same issue here on Fedora 40. Spent a bit of time debugging. Running from terminal with --no-sandbox and checking output I got to: DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.

@qichengzx
Copy link

I also had the same problem when I plugged in two USB devices, then I unplugged one of the devices, restarted ether, and there was no error when I selected the image file again

@Volcano-Dragon
Copy link

@qichengzx it worked for me also, Actually, I copied the iso file from USB pendrive to my system and then trying to open it in etcher, but got this (0, h.requestMetadata) error. Then I removed the USB and restarted the etcher and now no error.

I'm installing Linux Mint Cinnamon 21.6 on Windows 10 as my secondary OS.

Thanks to @qichengzx

@Eric-FR
Copy link

Eric-FR commented Jul 15, 2024

PC Acer. Windows 10 familly. 22H2.
I downloaded the default version proposed on belana website i.e. 1.19.21 (so, not supposed to be a beta).

image

@danielsigl
Copy link

@qichengzx it worked for me also, Actually, I copied the iso file from USB pendrive to my system and then trying to open it in etcher, but got this (0, h.requestMetadata) error. Then I removed the USB and restarted the etcher and now no error.

I'm installing Linux Mint Cinnamon 21.6 on Windows 10 as my secondary OS.

Thanks to @qichengzx

That worked. Had the same issue with win10 and newest version from Website. Removing USB flash and restarting program fixed issue while loading image. Thank you!

Till the image is loading very long, a loading spinner would be nice to be sure the program didn't crashed

@Eric-FR
Copy link

Eric-FR commented Jul 16, 2024

I downgraded to 1.18.11 to overcome the issue.

@rhlinka
Copy link

rhlinka commented Jul 19, 2024

PC Acer. Windows 10 familly. 22H2. I downloaded the default version proposed on belana website i.e. 1.19.21 (so, not supposed to be a beta).

image

I had same issue on Win 10. Even running as Administrator does not work as others mentioned here.

When I run with --no-sandbox option, it resolved the issue.
So, just run cmd on the directory where you have Etcher installed (it can be under /AppData/Local/balena_etcher - if not there, right click on the balenaEtcher in start menu and select "Open file location" - if it shows just shortcut, open file location of the shortcut until you see balena_etcher.exe)

Then start it with the option, e.g.:
C:\Users<the user>\AppData\Local\balena_etcher> balenaFetcher.exe --no-sandbox

@bexxxhb
Copy link

bexxxhb commented Jul 22, 2024

current version broken, can confirm this, windows 10, same "requestMetaData" error.

1.18.11 indeed still works, but sad for this project that no one fixes this longer existing error ...

@ruffieuxh
Copy link

Same problem on Ubuntu 22.04.4 LTS and AppImage.

Running on 1.18.11 worked flawlessly.

@meditrbt
Copy link

same on mac m1 sonoma 14.5

@savioazure
Copy link

PC Acer. Windows 10 familly. 22H2. I downloaded the default version proposed on belana website i.e. 1.19.21 (so, not supposed to be a beta).
image

I had same issue on Win 10. Even running as Administrator does not work as others mentioned here.

When I run with --no-sandbox option, it resolved the issue. So, just run cmd on the directory where you have Etcher installed (it can be under /AppData/Local/balena_etcher - if not there, right click on the balenaEtcher in start menu and select "Open file location" - if it shows just shortcut, open file location of the shortcut until you see balena_etcher.exe)

Then start it with the option, e.g.: C:\Users\AppData\Local\balena_etcher> balenaFetcher.exe --no-sandbox

It worked for me on w10

@GetsVR
Copy link

GetsVR commented Jul 26, 2024

Same problem on Ubuntu 22.04.4 LTS and AppImage.

Running on 1.18.11 worked flawlessly.

Win10. This was the only aforementioned method that worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests