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 · 204 comments
Open

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

wegank opened this issue Dec 21, 2023 · 204 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.

@amneiht
Copy link

amneiht commented Oct 8, 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
thank , it works on linuxmint 21

aethernet pushed a commit that referenced this issue Oct 8, 2024
rpmbuild strips executables by default when generating an rpm packge.
This was causing the JavaScript code bundled in the etcher-util file
to be removed, causing "Pkg: Error reading from file." whenever
etcher-util was called.

This in turn caused balena-etcher to generate the error message
`Error: (0, h.requestMetadata) is not a function` when attempting
to write an SD card.

This fixes the issue for RPM builds by replacing the `strip` command
with `true` so that rpmbuild no longer strips the executables and
the embeded code stays intact.

See: #4150

Signed-off-by: Richard Glidden <richard@glidden.org>
aethernet pushed a commit that referenced this issue Oct 9, 2024
rpmbuild strips executables by default when generating an rpm packge.
This was causing the JavaScript code bundled in the etcher-util file
to be removed, causing "Pkg: Error reading from file." whenever
etcher-util was called.

This in turn caused balena-etcher to generate the error message
`Error: (0, h.requestMetadata) is not a function` when attempting
to write an SD card.

This fixes the issue for RPM builds by replacing the `strip` command
with `true` so that rpmbuild no longer strips the executables and
the embeded code stays intact.

See: #4150

Signed-off-by: Richard Glidden <richard@glidden.org>
@thegreatyellow67
Copy link

Also same error opening source on LMDE6 with latest version balenaEtcher-1.19.25-x64.AppImage.

@SnowballV
Copy link

I tested the latest AppImage version, balenaEtcher-1.19.25-x64.AppImage, on Kubuntu 22.04.5.
With balenaEtcher-1.19.25-x64.AppImage, I still get "Error: (0, h.requestMetadata) is not a function".
balenaEtcher-1.18.11-x64.AppImage still works OK.

@usrthr
Copy link

usrthr commented Oct 11, 2024

I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso
Windows 11 10.0.22631 Build 22631
The error occurred when running from downloads or trying to use the iso from downloads folder
I created a folder in the root of C:\ , excluded folder from windows defender (this may or may not have been necessary, just including for completeness)

Subsequently, this has worked fine (twice)

Just adding in case this helps anybody out.

@buteomont
Copy link

buteomont commented Oct 11, 2024

Same issue here with version 1.19.25-x64.appImage. Running my old version 1.7.9-x64.appImage works.
--update--
Well, it seemed to work, but it threw the old checksum error when verifying. The disk seemed to boot once on my new Windows 11 laptop, but only once. Happened twice on two different cards. :-(

@andred1222
Copy link

I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso Windows 11 10.0.22631 Build 22631 The error occurred when running from downloads or trying to use the iso from downloads folder I created a folder in the root of C:\ , excluded folder from windows defender (this may or may not have been necessary, just including for completeness)

Subsequently, this has worked fine (twice)

Just adding in case this helps anybody out.

This worked for me, too! In addition, I started the balenaEtcher using 'Run as Administrator.'
Since then, I can also start the program in normal mode, and it works without errors.

@Peppernrino
Copy link

guys. stahp. this isn't a windows-related thread. linux. 1.18.13+ appimage. we already know about the windows fix. kthxbye. <3

@mwunderlich
Copy link

I've had the same issue with version 19 on Mac OS Monterey trying to flash an Ubuntu 24 LTS iso image. After downgrad to balenaEtcher 18.11., it worked.

@SamuelBanya
Copy link

I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso Windows 11 10.0.22631 Build 22631 The error occurred when running from downloads or trying to use the iso from downloads folder I created a folder in the root of C:\ , excluded folder from windows defender (this may or may not have been necessary, just including for completeness)
Subsequently, this has worked fine (twice)
Just adding in case this helps anybody out.

This worked for me, too! In addition, I started the balenaEtcher using 'Run as Administrator.' Since then, I can also start the program in normal mode, and it works without errors.

This isn't a Windows related issue. This GitHub issue is related to the Linux version of the 'AppImage'.

Please find or open a separate thread for the Windows release.

@AimadMoustajil
Copy link

AimadMoustajil commented Oct 20, 2024 via email

@SamuelBanya
Copy link

Hi Samuel, Thanks for sharing your experience and the details about the workaround you found! It’s great to see how others are troubleshooting similar issues. Could you clarify more on how this relates to future updates for Windows users? It would be helpful to understand if there’s any expected impact or changes we should be aware of. Looking forward to your insights! Best, Imad ‫في السبت، 19 أكتوبر 2024 في 7:41 م تمت كتابة ما يلي بواسطة ‪Samuel Banya‬‏ @.‬‏>:‬

I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso Windows 11 10.0.22631 Build 22631 The error occurred when running from downloads or trying to use the iso from downloads folder I created a folder in the root of C:\ , excluded folder from windows defender (this may or may not have been necessary, just including for completeness) Subsequently, this has worked fine (twice) Just adding in case this helps anybody out. This worked for me, too! In addition, I started the balenaEtcher using 'Run as Administrator.' Since then, I can also start the program in normal mode, and it works without errors. This isn't a Windows related issue. This GitHub issue is related to the Linux version of the 'AppImage'. Please find or open a separate thread for the Windows release. — Reply to this email directly, view it on GitHub <#4150 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEBMLJHQXOAMGOPSUPEO3UDZ4KRWRAVCNFSM6AAAAABA6XXUY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGEZTIMRWG4 . You are receiving this because you are subscribed to this thread.Message ID: @.
>

... It's NOT for the Windows version lol. The Windows users should file a separate thread as that's a separate OS altogether, and this issue is for the AppImage version on Linux.

@andyleemeuk
Copy link

I'm having the same issue attempting to use the latest AppImage 64 Bit on Mint Linux. I have switched to the DEB installer and that has mounted the image without any issues.

@MARCOadb
Copy link

Solved! Just check the compatibility settings of balena and you're good to go! balena solved

it worked for me!

@baeyensT
Copy link

Got the same issue on oct 30, 2024. did the make compatible with windows 8.... it works...
However, i'm using windows 10 ? the f?

@rdouma
Copy link

rdouma commented Nov 4, 2024

I ran into this issue on a Raspberry Pi 5 and could resolve it with this:

sudo usermod -aG disk $USER
sudo usermod -aG plugdev $USER

Maybe this helps some other poor soul.

@lenkinster
Copy link

I had the problem on windows. running belenaEtcher as admin helped.

@alMubarmij
Copy link

I have the same issue on Windows 10.
I tried many working ISO files.

@NikitaWeW
Copy link

restarting etcher worked

@firewiremb
Copy link

firewiremb commented Nov 20, 2024

Same issue with:
balenaEtcher-1.19.25-x64.AppImage
Kernel: 6.8.0-49-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble

Working for me without issues:
balenaEtcher-1.18.11-x64.AppImage

@RodrickM
Copy link

I have the same issue on Windows 10. I tried many working ISO files.

You may need to run it as Administrator.

@brettsy
Copy link

brettsy commented Nov 27, 2024

As @RodrickM says - RUN AS ADMINISTRATOR

@bahodirovich00
Copy link

Guys just open balena etcher with administrator

@SamuelBanya
Copy link

Guys just open balena etcher with administrator

Dude, this is a Linux based GitHub issue. Not the same OS.

@mokhov07
Copy link

This problem also applies to Mac OS.
I found a workaround to get the result
The terminal runs sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher.

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